# Technical implementation ## Indexing Ordinals We are in the process of developing custom indexers, essentially Bitcoin nodes designed to index the Ordinals and interpret BRC-20-defined protocols. Additionally, we have implemented customization to include ETH receiving addresses as metadata when recording 'transfer' on BRC-20 protocols for bridging functionality purposes. ## Multi-Signature Validation Multi-signature validation processes each inscription within the bundle, deducting gas fees and distributing them among validators based on their Bitcoin addresses. Valid operations in the Bitcoin network trigger multi-signature validation, updating the state and address balances in the Ethereum network. The validation degree and consensus mechanism are adjustable based on the system's security requirements ## Factory Smart Contract On the Ethereum side, we are actively developing a permissionless smart contract responsible for minting wrapped tokens on the ETH chain. As an integral step in our bridging process, the factory smart contract will dynamically create a token contract mirroring the original BRC-20 token name, prefixed with the letter "w" to signify its status as a wrapped asset. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ordify.gitbook.io/ordifyworld/ordify/orfy/technical-implementation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.