{"id":"arcium","version":1,"language":"en","title":"Arcium","hidden":false,"content":"**Arcium** is a decentralized network designed to support encrypted computations, focusing on providing privacy for on-chain applications and offering a verifiable, trustless framework for developers.[\\[1\\]](#cite-id-onysyhtz46h)[\\[2\\]](#cite-id-442cuqhdvxb)  \n$$widget0 [YOUTUBE@VID](dD_bfOqlNzs)$$  \n  \n# Overview  \n  \nArcium, founded in 2022 by [Yannik Schrade](https://iq.wiki/wiki/yannik-schrade), Julian Deschler, Nicolas Schapeler, and Lukas Steiner, aims to provide a decentralized confidential computing network. Initially called Elusiv, it operates a zero-knowledge privacy protocol on the [Solana](https://iq.wiki/wiki/solana) blockchain and has secured $9 million in funding across two rounds, including a strategic round led by Greenfield Capital.  \n  \nIn May 2024, Arcium launched its incentivized private testnet as part of its roadmap. The network is designed for secure data collaboration in sectors like [blockchain](https://iq.wiki/wiki/blockchain), healthcare, and AI, using a distributed node architecture to perform Multi-Party Computation (MPC) tasks while maintaining data encryption.  \n  \nArcium's framework on the [Solana](https://iq.wiki/wiki/solana) blockchain handles tasks such as computation scheduling and compensation. It aims to offer flexible MPC configurations, allowing users to tailor security and execution protocols for applications like AI model training and confidential data analysis.[\\[1\\]](#cite-id-onysyhtz46h)[\\[2\\]](#cite-id-442cuqhdvxb)[\\[3\\]](#cite-id-yl0ydu2oxc)[\\[4\\]](#cite-id-i5rtoijafjr)[\\[5\\]](#cite-id-b7owu6am01h)  \n![1500x500-31.jpeg](https://ipfs.everipedia.org/ipfs/QmVJfG3w4fkMWUYVgJJKArpCC8W35jbAQiic36S4Ceb2mn)  \n  \n# Architecture  \n  \nArcium’s architecture is designed to support distributed confidential computing. It breaks tasks into computation definitions, which are executed in Multi-Party Computation (MPC) environments (MXEs) on clusters of Arx nodes, functioning like hardware for secure processing.  \n  \nThe network is coordinated by programs running on the [Solana](https://iq.wiki/wiki/solana) blockchain, aiming to manage tasks through an on-chain mempool system. Compensation for computational services is handled on-chain, facilitating payments from customers to Arx operators and third-party delegators.[\\[6\\]](#cite-id-lp2y5p1u84a)  \n![Screenshot 2024-10-09 at 14.20.36.png](https://ipfs.everipedia.org/ipfs/Qma2yVhn5DfhPUdcD9UxcL4zAZcnfssEHTMLq74a3yn7hE)  \n  \n# Products  \n  \n## Multi-Party Execution Environments (MXEs)  \n  \nMultiparty Execution Environments (MXEs) aim to facilitate secure computations on encrypted data, enabling collaboration among multiple parties without revealing their inputs or outputs. Developers can customize the encryption schema based on the sensitivity of the data, generating a shared key for participating nodes.  \n  \nMXEs serve as fundamental components of the Arcium Network and can be classified as Single Use, which execute one computation before being discarded, or Persistent, allowing for reuse. Clusters of nodes confirm their capacity to process tasks, perform necessary preprocessing, and retrieve inputs from the [blockchain](https://iq.wiki/wiki/blockchain) for concurrent processing. The network supports various MPC protocols, including BDOZ, to enhance efficiency and security.[\\[5\\]](#cite-id-b7owu6am01h)[\\[7\\]](#cite-id-h01cxwu69v6)[\\[8\\]](#cite-id-kemc7rqrrv)[\\[9\\]](#cite-id-guu20cryr8o)[\\[10\\]](#cite-id-ikubufk9xn)[\\[11\\]](#cite-id-iejwa8q3od)[\\[12\\]](#cite-id-nxa04sf873)  \n  \n## Clusters  \n  \nClusters are designed as groups of Arx nodes that aim to utilize multiparty computation (MPC) for confidential operations. Customers can form Clusters based on various node properties, including reputation and computational capacity.  \n  \nDuring the creation of a Cluster, customers specify parameters such as maximum load and the number of Trusted Execution Environment (TEE)-enabled nodes. Most properties are fixed, with the exception of potential increases in load.  \n  \nNodes must provide consent to join a Cluster. In non-permissioned Clusters, a randomly selected node is added, and activation requires approval from all nodes. A Node Priority List is maintained for backup nodes.  \n  \nClusters manage cryptographic key operations through Distributed Key Generation (DKG) and can employ TEEs for enhanced confidentiality. Cluster forking enables remaining nodes to conduct separate computations if an MXE is ejected.  \n  \nMigration costs are shared among nodes, and intentions to shut down must be communicated to prevent penalties. Rewards are allocated based on stake delegation, with a Leader node collecting output shares for additional compensation. Permissioned Clusters enable organizations to oversee their node infrastructure.[\\[13\\]](#cite-id-1etbor7wzm6)[\\[14\\]](#cite-id-3j25ssn86ow)[\\[15\\]](#cite-id-zhj39s1j17m)[\\[16\\]](#cite-id-q9lwhed97sn)[\\[17\\]](#cite-id-rgtgus2tada)[\\[18\\]](#cite-id-c9hks9rueuw)[\\[19\\]](#cite-id-hjm9dfmspuu)[\\[20\\]](#cite-id-xldhourxtj)[\\[21\\]](#cite-id-latfcnw7mwn)[\\[22\\]](#cite-id-rz8l0dss8l)  \n  \n## Arx Node  \n  \nArx nodes function as fundamental components of the Arcium Network, aiming to facilitate distributed computing for complex tasks. Each node retains a single encrypted data fragment, employing the Multiparty Computation (MPC) protocol to enhance data privacy.  \n  \nNodes are associated with Node Operators, who may manage multiple nodes. Relevant metadata includes the node's IP, port, and jurisdiction codes. Arx nodes also manage key shares securely and may utilize Trusted Execution Environments (TEEs) to strengthen security.  \n  \nNode Operators generate income through self-delegation and fees from third-party delegations. Reputation is evaluated based on historical performance, with the network currently supporting the BDOZ MPC protocol and plans for future protocol expansions.  \n  \nMiddlelayer Nodes aim to connect off-chain data to computations, requiring a degree of trust from users. Reliable infrastructure is essential for node operation, and the support of TEEs may increase potential revenue opportunities.[\\[5\\]](#cite-id-b7owu6am01h)[\\[23\\]](#cite-id-nbhwh70jton)[\\[24\\]](#cite-id-ur30vs5hue)[\\[25\\]](#cite-id-vdoog93v96d)[\\[26\\]](#cite-id-m7uj4a0ni9e)[\\[27\\]](#cite-id-otgzp3i8t4b)[\\[28\\]](#cite-id-uzgbv4b9u5k)[\\[29\\]](#cite-id-nru05vkdxld)[\\[30\\]](#cite-id-xqbjprzpvgb)[\\[31\\]](#cite-id-4gr8ugkd3h8)[\\[32\\]](#cite-id-jozzxthvyk)  \n  \n## Computations  \n  \nThe Arcium Network differentiates between system and normal computations. System computations are designed to support network operations, including DKGSystemComputation for distributed key generation, MigrationSystemComputation for cluster migrations, and NonParticipationDetectionSystemComputation, which aims to trigger broader consensus when non-participation is detected.  \n  \nNormal computations refer to customer-initiated tasks associated with an MXE, defined in Computation Definitions that specify outputs and execution authority levels. The execution logic utilizes public or private circuits based on the BDOZ protocol for efficient cryptographic operations. Customers are responsible for setting parameters for data sources while maintaining data integrity and confidentiality. A deterministic pricing model facilitates cost pre-assessment and allows for priority enhancements through additional fees, with node operators voting to establish sustainable pricing.[\\[33\\]](#cite-id-p5yblgj08tm)[\\[34\\]](#cite-id-6rxwehjiwo9)[\\[35\\]](#cite-id-1z51wwdi2vw)[\\[36\\]](#cite-id-0612cz67u0bh)[\\[37\\]](#cite-id-dfw0tzscthh)[\\[38\\]](#cite-id-c5kckioky0w)[\\[39\\]](#cite-id-oii9v6j2kk)[\\[40\\]](#cite-id-oimm486v98r)  \n  \n## Decentralized Confidential Computing (DeCC)  \n  \nDecentralized Confidential Computing (DeCC) aims to ensure secure processing of sensitive data without exposure. It combines decentralization, which distributes data across multiple locations, with confidentiality measures to protect against unauthorized access. This approach addresses growing concerns over data privacy while facilitating secure processing in the [Web3](https://iq.wiki/wiki/web3) ecosystem.  \n  \nDeCC utilizes technologies such as Multi-Party Computation (MPC), [Zero-Knowledge Proofs (ZKPs)](https://iq.wiki/wiki/zero-knowledge-proofs-zkps), Fully Homomorphic Encryption (FHE), and Trusted Execution Environments (TEEs) to maintain data privacy during processing. The Arcium framework applies these DeCC principles to create a structure for encrypted computations, aiming to reduce the risk of data breaches by preventing any single entity from having full access to complete datasets.[\\[45\\]](#cite-id-rtep5r376ke)  \n![MXE-diagram-3.jpg](https://ipfs.everipedia.org/ipfs/QmVPHncbbw1wVkM1MJkM6eA2rwabq567Y22pqS494BMW8S)  \n  \n## Cerberus  \n  \nCerberus is a cryptographic protocol developed by Arcium for secure multiparty computation (MPC). It is built on the BDOZ MPC protocol and operates under the assumption of a dishonest majority, necessitating trust in only one honest participant per computation.  \n  \nThis protocol aims to incorporate an accountability mechanism through identifiable abort and oblivious transfer for trustless preprocessing. It allows for the identification and penalization of malicious actors in the network via a [staking](https://iq.wiki/wiki/staking) and slashing system based on cryptographic proofs.[\\[44\\]](#cite-id-87ynwi9vwnv)  \n  \n# Ecosystem  \n  \n## Solana Integration  \n  \nArcium utilizes [Solana](https://iq.wiki/wiki/solana), an open-source [blockchain](https://iq.wiki/wiki/blockchain) that facilitates [decentralized applications](https://iq.wiki/wiki/decentralized-application) and transactions. On-chain programs on [Solana](https://iq.wiki/wiki/solana) are responsible for managing the Arcium Network, which includes the registration of Arx nodes, computation processing, and financial activities such as payments and rewards.  \n  \nThe network implements a dual-mempool structure: the active mempool for computations ready for execution and the dependent mempool for computations awaiting the completion of others. This design aims to improve organization by directing computations to clusters of Arx nodes. While the integration is initially with [Solana](https://iq.wiki/wiki/solana), Arcium aims to support multiple [blockchains](https://iq.wiki/wiki/blockchain) in the future.[\\[5\\]](#cite-id-b7owu6am01h)[\\[41\\]](#cite-id-6p0vybw67v)[\\[42\\]](#cite-id-5jbh0gs21tg)[\\[43\\]](#cite-id-jwe4cf03v9b)  \n![Screenshot 2024-10-09 at 14.19.33.png](https://ipfs.everipedia.org/ipfs/QmQCZ6sKCku6rkg81da93hRTAWff68gXPQGePUBCDt1G2S)  \n  \n# Use Cases  \n  \nArcium's confidential computing network aims to enhance data security and privacy across various sectors. Key use cases include:  \n  \n* **AI**: Aims to facilitate the secure pooling of encrypted data for collaborative AI training while preserving the privacy of individual datasets.  \n* **Decentralized Finance (DeFi)**: Aims to encrypt [DeFi](https://iq.wiki/wiki/defi) actions and expand into [Real-World Assets (RWAs)](https://iq.wiki/wiki/real-world-assets-rwas) to promote compliance and protect user data.  \n* **Decentralized Physical Infrastructure Networks (DePIN)**: Aims to ensure secure handling of sensitive data in decentralized services without exposing the data.  \n* **Healthcare**: Aims to enable secure collaboration on sensitive patient data, facilitating analysis for personalized medicine while preserving privacy.[\\[5\\]](#cite-id-b7owu6am01h)[\\[44\\]](#cite-id-87ynwi9vwnv)","summary":"Arcium is a decentralized network for encrypted computations, ensuring privacy and verifiable trust for on-chain applications, primarily using Solana blockchain...","categories":[{"id":"organizations","title":"Organizations"}],"promoted":0,"tags":[{"id":"Protocols"},{"id":"Solana"}],"metadata":[{"id":"references","value":"[{\"id\":\"onysyhtz46h\",\"url\":\"https://arcium.com/what-is-arcium\",\"description\":\"website - What is Arcium\",\"timestamp\":1728445690497},{\"id\":\"442cuqhdvxb\",\"url\":\"https://tracxn.com/d/companies/arcium/__OdwSpw32MMiyih5e9Nfj42Kb3RiApHJNbunVqegIeyU#:~:text=Arcium%20was%20founded%20in%202022.\",\"description\":\"tracxn - Arcium\",\"timestamp\":1728445705539},{\"id\":\"yl0ydu2oxc\",\"url\":\"https://docs.arcium.com\",\"description\":\"docs - Overview\",\"timestamp\":1728445882396},{\"id\":\"i5rtoijafjr\",\"url\":\"https://pitchbook.com/profiles/company/510481-99#comparisons\",\"description\":\"pitchbook - Arcium\",\"timestamp\":1728445901028},{\"id\":\"b7owu6am01h\",\"url\":\"https://www.gate.io/learn/articles/what-is-arcium-all-you-need-to-know-about-arcium/3421\",\"description\":\"gate.io - What is Arcium\",\"timestamp\":1728445915474},{\"id\":\"lp2y5p1u84a\",\"url\":\"https://docs.arcium.com/getting-started/high-level-architecture-overview\",\"description\":\"docs - High-level Architecture Overview\",\"timestamp\":1728446066963},{\"id\":\"h01cxwu69v6\",\"url\":\"https://docs.arcium.com/multi-party-execution-environments-mxes/overview\",\"description\":\"docs - MEXs overview\",\"timestamp\":1728446521860},{\"id\":\"kemc7rqrrv\",\"url\":\"https://docs.arcium.com/multi-party-execution-environments-mxes/execution-workflow\",\"description\":\"docs - MEXs Execution workflow\",\"timestamp\":1728446533901},{\"id\":\"guu20cryr8o\",\"url\":\"https://docs.arcium.com/multi-party-execution-environments-mxes/computation-handling\",\"description\":\"docs - MEXs computation handling\",\"timestamp\":1728446552440},{\"id\":\"ikubufk9xn\",\"url\":\"https://docs.arcium.com/multi-party-execution-environments-mxes/mpc-protocols\",\"description\":\"docs - MEXs MPC Protocols\",\"timestamp\":1728446567393},{\"id\":\"iejwa8q3od\",\"url\":\"https://docs.arcium.com/multi-party-execution-environments-mxes/mxe-encryption\",\"description\":\"docs - MEXs MXE Encryption\",\"timestamp\":1728446584041},{\"id\":\"nxa04sf873\",\"url\":\"https://docs.arcium.com/multi-party-execution-environments-mxes/side-channel-attack-resistance\",\"description\":\"docs - MEXs Side-Channel-Attack Resistance\",\"timestamp\":1728446602694},{\"id\":\"1etbor7wzm6\",\"url\":\"https://docs.arcium.com/clusters/definition-and-purpose\",\"description\":\"docs - Clusters definition\",\"timestamp\":1728447013071},{\"id\":\"3j25ssn86ow\",\"url\":\"https://docs.arcium.com/clusters/cluster-formation\",\"description\":\"docs - Cluster Formation\",\"timestamp\":1728447023995},{\"id\":\"zhj39s1j17m\",\"url\":\"https://docs.arcium.com/clusters/admission-of-mxes\",\"description\":\"docs - Admission of MXEs\",\"timestamp\":1728447034616},{\"id\":\"q9lwhed97sn\",\"url\":\"https://docs.arcium.com/clusters/keyshare-distribution-and-security\",\"description\":\"docs - Keyshare Distribution and Security\",\"timestamp\":1728447051887},{\"id\":\"rgtgus2tada\",\"url\":\"https://docs.arcium.com/clusters/cluster-forking\",\"description\":\"docs - Cluster Forking\\n\",\"timestamp\":1728447067469},{\"id\":\"c9hks9rueuw\",\"url\":\"https://docs.arcium.com/clusters/cluster-migration\",\"description\":\"docs - Cluster Migration\\n\",\"timestamp\":1728447077556},{\"id\":\"hjm9dfmspuu\",\"url\":\"https://docs.arcium.com/clusters/rewards-distribution-to-nodes\",\"description\":\"docs - Rewards Distribution to Nodes\\n\",\"timestamp\":1728447087229},{\"id\":\"xldhourxtj\",\"url\":\"https://docs.arcium.com/clusters/reuse-of-existing-clusters\",\"description\":\"docs - Reuse of Existing Clusters\\n\",\"timestamp\":1728447105427},{\"id\":\"latfcnw7mwn\",\"url\":\"https://docs.arcium.com/clusters/permissioned-clusters\",\"description\":\"docs - Permissioned Clusters\\n\",\"timestamp\":1728447116761},{\"id\":\"rz8l0dss8l\",\"url\":\"https://docs.arcium.com/clusters/sybil-resistance\",\"description\":\"docs - Sybil Resistance\\n\",\"timestamp\":1728447126870},{\"id\":\"nbhwh70jton\",\"url\":\"https://docs.arcium.com/arx-nodes/node-configuration-and-setup\",\"description\":\"docs - Node Configuration and Setup\\n\",\"timestamp\":1728448674474},{\"id\":\"ur30vs5hue\",\"url\":\"https://docs.arcium.com/arx-nodes/keyshare-management-and-security\",\"description\":\"docs - Keyshare Management and Security\\n\",\"timestamp\":1728448688068},{\"id\":\"vdoog93v96d\",\"url\":\"https://docs.arcium.com/arx-nodes/self-claimed-hardware-specification\",\"description\":\"docs - Self-Claimed Hardware Specification\\n\",\"timestamp\":1728448705786},{\"id\":\"m7uj4a0ni9e\",\"url\":\"https://docs.arcium.com/arx-nodes/node-operation-incentives\",\"description\":\"Node Operation Incentives\\n\",\"timestamp\":1728448722829},{\"id\":\"otgzp3i8t4b\",\"url\":\"https://docs.arcium.com/arx-nodes/sub-node-delegation-rewards-distribution\",\"description\":\"docs - Sub-Node Delegation Rewards Distribution\\n\",\"timestamp\":1728448736884},{\"id\":\"uzgbv4b9u5k\",\"url\":\"https://docs.arcium.com/arx-nodes/performance-and-reliability-tracking\",\"description\":\"docs - Performance and Reliability Tracking\\n\",\"timestamp\":1728448753293},{\"id\":\"nru05vkdxld\",\"url\":\"https://docs.arcium.com/arx-nodes/multi-mpc-protocol-support\",\"description\":\"docs - Multi-MPC Protocol Support\",\"timestamp\":1728448763651},{\"id\":\"xqbjprzpvgb\",\"url\":\"https://docs.arcium.com/arx-nodes/middlelayer-nodes\",\"description\":\"docs - Middlelayer Nodes\\n\",\"timestamp\":1728448775825},{\"id\":\"4gr8ugkd3h8\",\"url\":\"https://docs.arcium.com/arx-nodes/trusted-execution-environments\",\"description\":\"docs - Trusted Execution Environments (TEEs)\\n\",\"timestamp\":1728448793756},{\"id\":\"jozzxthvyk\",\"url\":\"https://docs.arcium.com/arx-nodes/security-considerations\",\"description\":\"docs - Security Considerations\\n\",\"timestamp\":1728448805782},{\"id\":\"p5yblgj08tm\",\"url\":\"https://docs.arcium.com/computations/types-of-computations\",\"description\":\"docs - Types of Computation Tasks\\n\",\"timestamp\":1728449170272},{\"id\":\"6rxwehjiwo9\",\"url\":\"https://docs.arcium.com/computations/defining-a-computation\",\"description\":\"docs - Defining a Computation\\n\",\"timestamp\":1728449183526},{\"id\":\"1z51wwdi2vw\",\"url\":\"https://docs.arcium.com/computations/commissioning-a-computation\",\"description\":\"docs - Commissioning a Computation\\n\",\"timestamp\":1728449195544},{\"id\":\"0612cz67u0bh\",\"url\":\"https://docs.arcium.com/computations/computation-lifecycle\",\"description\":\"docs - Computation Lifecycle\\n\",\"timestamp\":1728449232868},{\"id\":\"dfw0tzscthh\",\"url\":\"https://docs.arcium.com/computations/computation-data\",\"description\":\"docs - Computation Data\\n\",\"timestamp\":1728449250375},{\"id\":\"c5kckioky0w\",\"url\":\"https://docs.arcium.com/computations/pricing\",\"description\":\"docs - Pricing\",\"timestamp\":1728449260151},{\"id\":\"oii9v6j2kk\",\"url\":\"https://docs.arcium.com/computations/censorship-resistance-and-slashing\",\"description\":\"docs - Censorship Resistance and Slashing\\n\",\"timestamp\":1728449270711},{\"id\":\"oimm486v98r\",\"url\":\"https://docs.arcium.com/computations/computation-units\",\"description\":\"docs - Computation Units (CUs)\\n\",\"timestamp\":1728449281270},{\"id\":\"6p0vybw67v\",\"url\":\"https://docs.arcium.com/solana-integration/overview-of-on-chain-coordination\",\"description\":\"docs - Overview of On-Chain Coordination\\n\",\"timestamp\":1728449446990},{\"id\":\"5jbh0gs21tg\",\"url\":\"https://docs.arcium.com/solana-integration/on-chain-mempools\",\"description\":\"docs - On-Chain Mempools\\n\",\"timestamp\":1728449457541},{\"id\":\"jwe4cf03v9b\",\"url\":\"https://docs.arcium.com/solana-integration/other-blockchains\",\"description\":\"docs - Other Blockchains\\n\",\"timestamp\":1728449481375},{\"id\":\"87ynwi9vwnv\",\"url\":\"https://arcium.com\",\"description\":\"Arcium website\",\"timestamp\":1728449734836},{\"id\":\"rtep5r376ke\",\"url\":\"https://blog.arcium.com/what-is-decc-decentralized-confidential-computing/\",\"description\":\"blog - Decentralized Confidential Computing (DeCC)\",\"timestamp\":1728450624948}]"},{"id":"website","value":"https://arcium.com"},{"id":"twitter_profile","value":"https://x.com/ArciumHQ"},{"id":"youtube_profile","value":"https://www.youtube.com/@ArciumNetwork/featured"},{"id":"discord_profile","value":"https://discord.com/invite/arcium"},{"id":"github_profile","value":"https://github.com/elusiv-privacy"},{"id":"commit-message","value":"added founder links"},{"id":"previous_cid","value":"QmQN3s529rZqjPBDDN8tAkcN86vqAXQNpwgDYAmkgkMB96"}],"user":{"id":"0xf32ECD5c8f5633212f1a25A3931aDDc0CEc42938"},"author":{"id":"0xf32ECD5c8f5633212f1a25A3931aDDc0CEc42938","profile":{"username":"Tara","avatar":"QmcYZFprbPwBjahvN3cjVsdTGtYgCx8jM1Myeb7yYJyeUF"}},"media":[{"name":"dD_bfOqlNzs","id":"https://www.youtube.com/watch?v=dD_bfOqlNzs","size":"0","type":null,"source":"YOUTUBE"},{"name":"1500x500-31.jpeg","id":"QmVJfG3w4fkMWUYVgJJKArpCC8W35jbAQiic36S4Ceb2mn","size":"0.03","type":"GALLERY","source":"IPFS_IMG"},{"name":"MXE-diagram-3.jpg","id":"QmVPHncbbw1wVkM1MJkM6eA2rwabq567Y22pqS494BMW8S","size":"0.03","type":"GALLERY","source":"IPFS_IMG"},{"name":"Screenshot 2024-10-09 at 14.19.33.png","id":"QmQCZ6sKCku6rkg81da93hRTAWff68gXPQGePUBCDt1G2S","size":"1.23","type":"GALLERY","source":"IPFS_IMG"},{"name":"Screenshot 2024-10-09 at 14.20.36.png","id":"Qma2yVhn5DfhPUdcD9UxcL4zAZcnfssEHTMLq74a3yn7hE","size":"1.13","type":"GALLERY","source":"IPFS_IMG"}],"views":18,"events":[],"linkedWikis":{"founders":["yannik-schrade"],"blockchains":["solana"]},"founderWikis":[],"blockchainWikis":[{"id":"solana","title":"Solana"}],"ipfs":"QmQN3s529rZqjPBDDN8tAkcN86vqAXQNpwgDYAmkgkMB96","transactionHash":"0x07801989d1b2e5229e5c23b8364be54688a9bc6cafb3848fee52d5954564a449","created":"2024-10-09T05:34:03.600Z","updated":"2024-10-09T05:34:03.600Z","images":[{"id":"QmaU61X1Gw2JpSjEsnXWz2P1jBSqMYzhpXgBcSFwgFQ1x5","type":"image/jpeg, image/png"}]}