Summary
This issue tracks the introduction of RoK, a native token for ResilientDB, which will serve as the foundation for transaction fees, smart contract execution costs, and future economic mechanisms within the ecosystem.
Today, ResilientDB provides smart contract deployment, execution, and account balance management, but does not have a formalized native asset with standardized transfer and fee semantics. RoK aims to establish a consistent economic layer that can be extended over time while remaining aligned with ResilientDB's existing architecture.
Motivation
As the project continues to evolve, introducing a native token provides several benefits:
- Establishes a standardized mechanism for transaction and execution costs.
- Creates a foundation for gas accounting and resource usage pricing.
- Enables native value transfer between accounts.
- Provides a basis for future incentives, governance, and ecosystem growth.
- Aligns ResilientDB more closely with expectations from modern blockchain and smart contract platforms.
Scope
The initial work will focus on introducing RoK within the smart contract execution path and account model while minimizing disruption to existing functionality.
The implementation is expected to include:
- Native RoK account balances.
- Account persistence and ownership through cryptographic identities.
- Native RoK transfer functionality.
- Balance management APIs and tooling support.
- Foundations for future fee and gas accounting.
The exact architecture, implementation details, migration strategy, and API changes will be documented and discussed through subsequent design discussions and pull requests.
Expected Outcome
Upon completion, ResilientDB will have a native token layer that supports:
- Account-based ownership of RoK.
- Native balance tracking.
- Secure transfers between users.
- Future integration with transaction fees and gas mechanisms.
This issue serves as the umbrella tracking item for the RoK initiative. Implementation details and design decisions will be tracked through linked pull requests and follow-up issues.
Related Work
- Native account management
- Balance persistence
- RoK transfer operations
- Smart contract integration
- Fee and gas framework (future work)
- Wallet and ecosystem tooling support
Summary
This issue tracks the introduction of RoK, a native token for ResilientDB, which will serve as the foundation for transaction fees, smart contract execution costs, and future economic mechanisms within the ecosystem.
Today, ResilientDB provides smart contract deployment, execution, and account balance management, but does not have a formalized native asset with standardized transfer and fee semantics. RoK aims to establish a consistent economic layer that can be extended over time while remaining aligned with ResilientDB's existing architecture.
Motivation
As the project continues to evolve, introducing a native token provides several benefits:
Scope
The initial work will focus on introducing RoK within the smart contract execution path and account model while minimizing disruption to existing functionality.
The implementation is expected to include:
The exact architecture, implementation details, migration strategy, and API changes will be documented and discussed through subsequent design discussions and pull requests.
Expected Outcome
Upon completion, ResilientDB will have a native token layer that supports:
This issue serves as the umbrella tracking item for the RoK initiative. Implementation details and design decisions will be tracked through linked pull requests and follow-up issues.
Related Work