When weβre writing our blueprints weβll eventually come to a point where we need to think about how a component can be given authority to perform some kind of action. The user badge pattern(user-bad
Legacy documentation: Design Patterns
A common desire of blockchain applications is to send tokens to users β whether from dApp smart contract or backend system. Maybe you're building a fully featured dApp, maybe you're an exchange, or ma
This may be looked at as a best-practice to blueprint developers hoping to benefit from developer royalties, rather than a design pattern. Non the less, this is an important best practice and warrants
This pattern builds upon the user badge pattern(user-badge-pattern.md) and could be considered as one of its use cases. The problem which this pattern solves is the problem of getting funds from com
The class of problems that this pattern solves is quite simple to describe but complex to think about and solve. However, this pattern solves this class of problems in such a simple, elegant, and uniq
The problem that this pattern solves is the problem of how to tell that somebody is an admin in your system, or more generically, how to tell that a user has the authority to perform a certain action