Namespace Actions
Namespace Initialization
Creating a Namespace should be the first step when designing how to store state with Raindrops. During Namespace creation, it's possible to configure many variables, like which Staking mints are allowed to be staked, caching parameters and naming schemes. Creating Namespace Gatekeepers is also a configurable aspect to initialization, these Gatekeepers can have filters that determine which Artifacts are eligible to be joined to your new Namespace.
Namespace Joining
After a Namespace is created, next create a Raindrops artifact, these can be Item's, Matches or Players. After an Artifact is created, try joining it to a Namespace. Joining artifacts to a namespace allow you to associate and index them in different ways depending on your use case. It's possible to query for all Artifacts that belong to a given Namespace very easily.
Namespace Caching
Artifacts which are joined to a Namespace can subsequently be cached to the same Namespace. If an Artifact needs to be removed from a Namespace, it's first removed from the namespace's cache. Caching enables easy lookup of an Artifact's Namespaces.
Full Artifact Namespace Lifecycle
These directions use the CLI, the example configuration is simply to understand the JSON structure you need to provider, use your own payloads.
Setup
Artifact Created
Namespace Initialized
Namespace Gatekeeper created
Artifact Joins a Namespace
Cache Artifact to the Namespace
Artifact Removed from Namespace Cache
Artifact Leaves a Namspace
Last updated