Blockchain-Powered Luxury Ownership
"Secure Ownership, Verified Authenticity, Powered by Blockchain."
About
The problem it solves We provides a blockchain-powered platform for secure, transparent, and trusted ownership transfers of luxury goods such as watches and bags. It addresses critical challenges in the luxury market, including fraud prevention, authentication, and transparency by creating a decentralized system that records and verifies the authenticity of each item. Using Ethereum and Ether (ETH) for payments, the platform ensures that funds are held securely in escrow until all conditions, such as item verification, are met. Key problems solved: - Fraud prevention through immutable records of authenticity and ownership. - Transparent ownership transfers via automated smart contracts. - Secure high-value transactions with escrowed ETH payments. - Global access and seamless cross-border transactions using Ethereum. - Dispute resolution mechanisms built into the platform to protect both parties in case of disputes.
How it's made
Challenges we ran into The issue we faced was the high cost of gas fees on the Ethereum mainnet during periods of network congestion. Each action, including initiating payments, transferring ownership, and verifying conditions, involved multiple contract interactions, leading to high transaction costs and delays for users.To address the high gas fees and slow transaction speeds, we integrated Scroll, a Layer 2 scaling solution for Ethereum. This allowed us to move most of the transaction processing off-chain, reducing both gas fees and congestion-related delays. Scroll maintains Ethereum’s security while providing cost-effective and faster transactions. One of the challenges we faced during the development was related to smart contract verification on Scrollscan after a successful deployment. Although the contract was successfully deployed to the Scroll network, the verification process failed with an error stating that it was "unable to locate contract code" for the given contract address. We carefully ensured that the Solidity compiler version used during deployment matched the version selected during the verification process. Additionally, we aligned the optimization settings used in the contract deployment with those used in the verification process. By addressing all the possible issues, sadly, we still failed to verify and publish our smart contract due to the bug of the platform. Hopefully, there will be enhancement in showing the reason of error to helps hackers to be more understand their failing of verification.