Comments (3)
My 2 cents:
Restricting the character sets for bucket names in our smart contract is irrelevant to me. Front-end applications typically sanitize input to mitigate security risks (such as XSS), making the risk of security issues from uncleaned names practically non-existent. Furthermore, imposing such restrictions could prevent users from using international characters or special symbols, which might be essential for their needs.
Additionally, in blockchains, the larger the data, the higher the cost, creating a natural deterrent against abuses such as entering extremely long strings. In my sense, this cost-based deterrent is an effective and direct way to discourage abuse without needing additional restrictions.
Important to note that if the security analysis recommendation were implemented, it would need to apply to all textual fields across all our smart contracts, including the cognitarium
, making the implementation extremely significant and impactful.
from contracts.
I totally agree with you @ccamel, this would bring an opinionated API on matters that are in the scope of the network's token model & the client's responsibility.
I'd be in favour of closing this one.
from contracts.
The team has reviewed this issue and agreed to decline it.
from contracts.
Related Issues (20)
- 🤯 Cognitarium: Prevent blank nodes conflicts HOT 3
- 🤯 Cognitarium: Remove blank node filtering from messages HOT 2
- 💚 Implement Crate Publication in CI Upon Release HOT 1
- 🛡️ Denial of Service (DOS) via Front-Running Leads to Law Stone Initialization Failure HOT 1
- 🛡️ Unauthorized Object Deletion Triggers Denial of Service HOT 3
- 🛡️ Unrestricted Access to Break_Stone if Deployed without admin HOT 2
- 🛡️ Arithmetic Overflow in CosmWasm-Std Affects OKP4 Contracts HOT 2
- 🛡️ Format Restriction in Data Submission Leads to Underutilization of RDF Options HOT 3
- 🛡️ Not All Storage Elements Are Exposed Through Queries HOT 1
- 🛡️ Insufficient information in Events HOT 5
- 🛡️ Lack of Storage Address Validation in Law-Stone Instantiation HOT 5
- 🛡️ Inaccurate Compressed Size Tracking on Object Deletion in Objectarium
- 🛡️ Inadequate Input Validation in Objectarium Contract Instantiation HOT 3
- 🛡️ Insufficient Error Handling in Object Access Within Objectarium HOT 4
- 🛡️ Arbitrary Fund Acceptance in OKP4 Contracts
- ♻️ Rename "metadata" field in SubmitClaims struct to "claims" HOT 1
- 🗜️ Inconsistency in Object Storage with Different Compression Status HOT 2
- 🤯 Filter query with expressions
- 🌐 Extend VC context
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from contracts.