DOCSEARCHbyAlgolia
Submit Docs

Core Improvement Proposals

website·Indexed 32 days ago

https://cip.coreblockchain.net/

The official registry of Core Improvement Proposals (CIPs) for the Core platform. This documentation defines standards for the Core Blockchain, including token standards (CBC-20, CBC-721, CBC-1155), cryptography schemes (CIP-98), HD-wallet derivation (CIP-99), and address standards (ICAN). It also outlines the CIP workflow, editor responsibilities, and technical specifications for smart contract interfaces and on-chain metadata.

Tokens
35.7K
Snippets
114
Records
211
Agent score
56%

What's inside CIP

  1. Overview of the CBC-1155 Multi Token Standard

    The CBC-1155 standard provides a single smart contract interface capable of representing any number of fungible, non-fungible, and semi-fungible token types. Unlike CBC-20 (which requires separate contracts per token) or CBC-721 (which manages a single collection of non-fungibles), CBC-1155 allows each token ID (_id) to represent a distinct token type with its own metadata, supply, and attributes. This design enables batch transfers of multiple token types in a single transaction, reducing gas costs and simplifying atomic swaps/escrows.

  2. Overview of the PriceFeed Decentralized Oracle

    The PriceFeed contract acts as a decentralized oracle that aggregates asset price data submitted by authorized nodes. It is designed to provide reliable, up-to-date price information for DeFi platforms, reducing reliance on single data providers to prevent manipulation and ensure stability for collateralization and liquidation processes.

  3. Overview of the CBC-1820 Pseudo-introspection Registry

    The CBC-1820 Registry is a universal smart contract that allows any address (whether a smart contract or a regular account) to register the interfaces it supports and the specific smart contract responsible for implementing those interfaces. This allows external entities to query if a specific address implements a given interface and identify the handler contract. It is designed to be deployed on any Core network, with its network-specific ICAN address published for discovery.

  4. Overview of the CoreToken (CIP-200) Standard

    CoreToken is a multifaceted extension of the BaseToken contract designed for the Core Blockchain ecosystem. It integrates several specialized token functionalities into a single, CBC20-compatible contract to support diverse applications such as DeFi and governance. It inherits standard CBC20 functions and adds the following capabilities:

    • WrapperToken: Ability to wrap and unwrap other CBC20 tokens.
    • EquivalentToken: Integration with external price feeds to maintain value equivalence.
    • ChequableToken: Issuance and cashing of cheques for controlled token allowances.
    • BountiableToken: Systems for assigning and executing token-based bounties.

  5. Overview of Core Signature Verification Standard (CIP-712)

    CIP-712 provides a deterministic method for hashing and signing typed structured data in Core Blockchain applications. It ensures that signers can see named fields instead of opaque byte strings and provides domain separation between applications, contracts, and networks to prevent cross-domain replay attacks. While it follows the EIP-712 data model and \x19\x01 framing, it is NOT byte-for-byte compatible with Ethereum due to the use of Core network IDs, 22-byte addresses, SHA3-256 hashing, and EDDSA signatures.

  6. Overview of the Diamond Multi-Facet Proxy Pattern

    A Diamond is a stateful facade smart contract that uses delegatecall to execute functions provided by separate, stateless contracts called Facets. This pattern allows for modularity, upgradeability, and the ability to bypass the network's maximum contract size limit, as each facet is deployed independently. A single facet can be shared across multiple diamonds.

  7. Overview of the CIP-4626 Tokenized Vaults Standard

    CIP-4626 is a standard for tokenized vaults that represent shares of a single underlying CIP-20 token. It extends the CIP-20 token standard to provide a consistent API for depositing, withdrawing, and reading balances.

    Key architectural requirements:

    • All CIP-4626 vaults MUST implement CIP-20 to represent shares.
    • Vaults MUST implement CIP-20 optional metadata extensions (name and symbol).
    • Vaults MAY implement CIP-2612 to improve the user experience for approving shares.
    • If a vault is non-transferable, it may revert on transfer or transferFrom calls.

  8. Overview of the ChequableToken (CIP-106) standard

    ChequableToken is an extension of the CBC20 token standard on the Core Blockchain (Ylem version >0.8.0). It introduces a cheque system that allows token holders to authorize third-party spenders to withdraw a specific amount of tokens. Unlike traditional CBC20 allowances, these authorizations are time-bound and tracked via nonces to prevent double-spending and increase security for deferred or conditional transfers.

  9. CIP-4626 Compatibility and Token Standards

    CIP-4626 is fully backward compatible with the CIP-20 standard. Vaults are expected to implement CIP-20 for their share tokens, ensuring that token approvals and balance calculations are consistent. This allows Vault shares to be compatible with any existing CIP-20 ecosystem tool. For legacy Vaults that do not support CIP-4626, developers can implement wrapper adapters to achieve compatibility.

  10. Understand the purpose of Core Improvement Proposals (CIPs)

    Core Improvement Proposals (CIPs) are the primary mechanism for proposing new features, gathering community technical feedback, and documenting design decisions within Core. Because they are maintained as text files in a versioned repository, the revision history of a CIP serves as the official historical record of a feature's evolution. For implementation maintainers, CIPs provide a way to track and communicate the progress of their work; it is recommended that maintainers provide a list of implemented CIPs to help end users determine the status of a specific library or implementation.

  11. Understand the purpose of a Core Improvement Proposal (CIP)

    A Core Improvement Proposal (CIP) is a formal design document used to introduce new features, technical specifications, or process changes to the Core community and its environment. A CIP must provide a clear technical specification and a rationale for the proposal. The author of a CIP is responsible for building community consensus and documenting any dissenting opinions regarding the proposal.

  12. Understand the role and responsibilities of CIP Editors

    CIP Editors are members of the GitHub team — CIP. Their role is strictly administrative and editorial; they do not judge the technical merits of a proposal, but ensure it meets the repository's standards for quality and structure.

    For every new CIP submission, an editor is responsible for:

    1. Technical Coherence: Reviewing the CIP to ensure it is sound, comprehensive, and technically coherent.
    2. Accuracy: Ensuring the title accurately describes the content.
    3. Quality Control: Reviewing spelling, grammar, sentence structure, GitHub-flavored Markdown markup, and code style.

    If a CIP does not meet these standards, the editor returns it to the author with specific revision instructions.