Welcome to the EOSIO Specifications Repository

Scope: The EOSIO Specifications Repository aims to provide high level design details for many of the ideas discussed in the Strategic Vision Document

Goal: We aim to communicate our technical design choices and seek feedback from the community on our approach. However, we may not be able to respond to every element of feedback or synthesize all the feedback into a consensus approach.

Details: The software design docs are being released as part of EOSIO Labs. The design docs are forward looking guesses when they are published on how we might want to realize the feature/functionality needs. We make no guarantees about implementing it as designed or even keeping the specs updated to match the eventual design choices. Interested members of the community can engage with us on the technical design details of how we are thinking about implementing various pieces of functionality.

Repo mechanics and feedback: Each spec will be a separate markdown file similar to this one. Community members can create issues to provide feedback on the various specifications. Issues can be created using the provided issue template.

About EOSIO Labs

EOSIO Labs repositories are experimental. Developers in the community are encouraged to use EOSIO Labs repositories as the basis for code and concepts to incorporate into their applications. Community members are also welcome to contribute and further develop these repositories. Since these repositories are not supported by Block.one, we may not provide responses to issue reports, pull requests, updates to functionality, or other requests from the community.

Documents

Key:

• . = Still being drafted
• R = Ready for feedback

In dependency order:

• R Smart Contract Modules
• R Deprecate Deferred
• R Sized Data (ABI 1.2)
• R Tagged Data
• . Flexible Notifications
• R Synchronous Calls
• R Query Consumption
• R Subjective Data
• R Get Producer
• R Contract Pays
• R Contract Authentication
• R Forwarding Authorizations
• R Enhanced Token
• R Configurable WASM Limits

Not in dependency order:

• R Key-Value Database
  • R Key-Value Database Intrinsics
• R Regions

Deprecations:

• require_recipient: Flexible Notifications
• Deferred Transactions: Deprecate Deferred

Practices to Consider (PTC):

• . Alternative Uses for WebAuthN Signatures

Contributing

Contributing Guide

Code of Conduct

Important

All material is provided subject to this important notice and you must familiarize yourself with its terms. The notice contains important information, limitations and restrictions relating to our software, publications, trademarks, third-party resources and forward-looking statements. By accessing any of our material, you accept and agree to the terms of the notice.