Scrypto

Asset-oriented programming: resources, auth, testing, and design patterns.

The main article for this category is Scrypto.

The following 9 pages are in Scrypto.

1. Scrypto Fundamentals

Scrypto is built on asset-oriented programming – a paradigm where digital assets are first-class primitives managed by the Radix Engine , not arbitrar…

2. Resources, Vaults, and NFTs

A resource is any digital asset on Radix – tokens, NFTs , badges , LP tokens, etc. Unlike Solidity where tokens are contract state, Radix resources ar…

3. Authorization and Access Rules

In most smart contract platforms, access control is based on the caller's address – a pattern that leads to fragile permission systems and common expl…

4. Events, Metadata, and Royalties

Components can emit events during transaction execution. Events are encoded in SBOR and stored in the transaction receipt – useful for indexing, analy…

5. Testing Scrypto Blueprints

Once your development environment is set up, the next step is understanding the Scrypto development workflow: creating packages, writing blueprints ,…

6. Vault and Resource Patterns

Radix enforces a strict invariant: every resource must exist inside a container at all times. There are two container types: Vaults (permanent, on-led…

7. Multi-Component Architecture

Scrypto separates the concept of "smart contract" into two distinct things: blueprints (reusable templates) and components (live instances on the ledg…

8. Oracle Integration

Scrypto components execute deterministically on the Radix Engine and can only access data already present on the ledger – they cannot make HTTP calls…

9. Permissioned and Regulated Assets

Some assets are not meant to move freely. A tokenised bond may only be transferable between investors who have passed KYC; a credential must stay in t…