Scrypto

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

Three Scrypto badge patterns: user badges for people, actor virtual badges for components, and transient badges that force a call order.

How a Radix dApp pays users who are not in the transaction: return buckets, badge and claim, authorized depositors, and the account locker.

The types a Scrypto blueprint works with, Decimal arithmetic and rounding, and what a blueprint can ask the engine at run time: epoch, clock, addresses, hashes, logs.

The checks the Radix docs ask of every Scrypto blueprint before mainnet: proofs, state growth, Decimal maths, auth, owners, metadata and builds.

A resource is any digital asset on Radix – tokens, NFTs, badges, LP tokens, etc.

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

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

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

Radix enforces a strict invariant: every resource must exist inside a container at all times.

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

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

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 the…