EthDenver: Speaking, Workshops, Hackathons
Swap native tokens or bridge across networks without signing transactions with smart contracts. Send $ONE tokens to a plain wallet address on usdc.country and receive $USDC. Optionally specify a target network and a wallet address one/0x… in the transaction field calldata to bridge. Support the top 1000 networks and assets via auctioned domain names such as btc.country and eth.country.
Easy onboarding with any wallets to acquire any native tokens. Eliminate security risks with smart contracts, transaction signing, frontend deploys, bridge custody, asset whitelists, or miner extractions. Like Over-The-Counter (OTC) services but via inscription, or intent-based protocols like Uniswap X, Anoma, Chainflip, Across. See Harmony 2024 Roadmap.
How to secure tokens for recurring wallet transactions against key loss or guardian theft? Have a hot wallet with a capped amount, then reload from a social wallet guarded by 2 or more operators. How to make the social reloading as simple as a send transaction? Have a minimal smart contract (almost dumb!) for the single purpose of token custody and social reload. Similar to multisig smart wallets like Gnosis Safe and Argent, but only a few lines of code fully instantiated with predefined transfer amounts and operator addresses.
No need for transaction indexing or web frontend needed. No need for contract signing or wallet support. No upgradable contracts, security councils, governance tokens, or emergency votes. Simply substitute all variables and shortcut all logics from a program template – like a whole-program-optimization or partial evaluation in compilers.
The absolutely bare example is securing against key loss with two social wallets, that is, a 1-of-2 multisig safe but minimal onchain. First, anyone can send $100k ONE tokens to the contract’s custody address to initialize. Second, either of predefined wallets A or B can send 0 ONE token to the contract’s reload address to trigger sending $100 ONE to a predefined hot wallet C. Third, optionally, either can send a token to the contract’s recovery address to trigger sending all remaining tokens to the other operator.
Let a smart contract access the calldata field of a simple send transaction as a parameter for dynamic customization. Inscription games begin.
Send an inscription transaction with your favorite tweet to the lottery address 0x3abf101D3C31Aec5489C78E8efc86CaA3DF7B053. A daily winner gets 1000 ONE tokens and 100 HOG tokens as of Jan 18th, 2024.
The winner is the latest transaction with the closest ending 2 digits to the starting inscription transaction that announces the daily prize amount. Your tweets will be displayed on the premium 2-letter .country domains.
For example, if the starting transaction id is 0x…aa, the latest inscription at ae.country wins over that at f5.country – assuming no inscription at aa.country and because the hexdecimals 0xab - 0xaa = 1 is smaller than 0xf5 - 0xaa = 75.
The daily prize amount and the participating transactions are on the explorer page for the lottery address. Later, i.country will host a leaderboard and special announcements for side quests.