Etherscan has just rolled out GPT4 integration for learning about how verified contracts work on Ethereum mainnet. Great, since non-devs could read, but have to rely on devs to raise flags about fishy contracts.
Here's a breakdown of the @niftycannon bulk NFT transfer contract.
A vote for Friday is a vote for Freedom! It's a vote against the puppy-devouring monsters that live under your bed. For everything that is good and decent. In short, please vote for Friday.
Paid for by the Cliff Wants to Listen to Web3 Galaxy Brain on Friday Mornings super PAC.
So you find yourself at https://t.co/ByPM8dJ68N and suddenly need to send some #NFTs to one or more wallets. A visionary tech mogul you met at the bar, the first ten people at the event who respond to your tweet, me even. The possibilities are endless. 🎉
https://t.co/20VmHjNmfh
Ok, folks, the current release candidate for Nifty Cannon MVP is up at https://t.co/QEPdLynaNK. If you have ERC721s and/or ERC1155s on Rinkeby testnet, please have a go at sending and claiming them using airdrop, will-call, and transferable ticket. Gas estimates are for mainnet.
@justinaversano@seaofarrows @AxieKing In the future, a contract upgrade will check a Rampart contract where you can essentially put your address on a 'do not send list'.
@justinaversano@seaofarrows @AxieKing Someone can transfer an NFT to you right now, without your being able to bounce it. Airdrops from the cannon go directly to recipient wallets. It's up to the sender to choose to follow etiquette. There is the option to send for will call, where recipient claims.
@favy_qwin CAUTION: The official support address for Metamask is: [email protected]. Likely the above email address is a phishing scam intended to suck in folks and get them to reveal their seed phrases.
After the #Ethereum London fork and ERC-1559 going into effect, folks have been complaining that the UI in Metamask is a bit confusing with regard to gas fee structure and tx speed. The Nifty Cannon UI has been updated to make things a very clear before sending or claiming.
if you need a lot of functionality in one place and max contract size foils all your plans, look into the Diamond. But if the contract you want to proxy won't get large enough to truly need to be carved into pieces, maybe use a Minimal Proxy. DYOR.
https://t.co/dMSYOXHt94
By breaking all three huge contracts into six and huddling them behind a Diamond Proxy, we not only solved the max size problem for all three contracts, but we have a single address to listen to events, making monitoring of the system as it expands much easier.
👇
@primal_cypher@opensea At first the easiest implementation for each step is being built, but the architecture of the app is one that expects any number of strategies could be available at any step. Once the app is out, I intend to add other strategies as I can. Probably a DAO can vote on which ones.
OMG, this is the first Saturday I've had off in ages. Reconnecting to the project and realizing I need a design for transferable tickets when they're show on secondary markets like @Opensea. Whaddya think?
@primal_cypher@opensea Each of the steps necessary to say what you want to send to who and how are places where it could be done several ways. For instance, if you know your recipients, you can enter a list. But another strategy might be to send to holders of a given ERC-20 token.
👇