ignore 🥶 (@ignored24) header
ignore 🥶 (@ignored24) profile picture
Joined August 2023
Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)Photo by ignore 🥶 (@ignored24)
From zero to hero is possible Thanks to @HodlNFT1K
1
1
1
11
1,562
ignore 🥶 retweeted
Introducing the new collector experience, now live on pocketpad.io. Explore our new home page, browse through your gallery with a more enhanced view, check your notifications so you never miss a chance to grow your collection, and more!
17
21
3
81
5,056
ignore 🥶 retweeted
𝚆𝚎'𝚛𝚎 𝚟𝚎𝚛𝚒𝚏𝚒𝚎𝚍 𝚘𝚗 @Opensea 𝙾𝚞𝚛 𝚝𝚒𝚖𝚎 𝚒𝚜 𝚐𝚎𝚝𝚝𝚒𝚗𝚐 𝚌𝚕𝚘𝚜𝚎𝚛 𝚎𝚟𝚎𝚛𝚢 𝚍𝚊𝚢 𝟻𝟶% 𝙶𝚃𝙳 𝚊𝚕𝚕𝚘𝚌𝚊𝚝𝚎𝚍 𝙾𝚏𝚏𝚒𝚌𝚒𝚊𝚕 𝚕𝚒𝚗𝚔: opensea.io/collection/spacer…
355
655
20
1,147
18,023
50% GTD allocated ? Noo dont make me secara 😭 i need my own pfp
𝚆𝚎'𝚛𝚎 𝚟𝚎𝚛𝚒𝚏𝚒𝚎𝚍 𝚘𝚗 @Opensea 𝙾𝚞𝚛 𝚝𝚒𝚖𝚎 𝚒𝚜 𝚐𝚎𝚝𝚝𝚒𝚗𝚐 𝚌𝚕𝚘𝚜𝚎𝚛 𝚎𝚟𝚎𝚛𝚢 𝚍𝚊𝚢 𝟻𝟶% 𝙶𝚃𝙳 𝚊𝚕𝚕𝚘𝚌𝚊𝚝𝚎𝚍 𝙾𝚏𝚏𝚒𝚌𝚒𝚊𝚕 𝚕𝚒𝚗𝚔: opensea.io/collection/spacer…
1
49
The current Eth core dev concern going around and the narrative of accessible, store of value, consumer friendly crypto that is accessible and safe against tradfi attack vectors really does NEED a surface area people can use naturally ~@huntclubhero said
This week’s tokenization posts (ETH as a programmable store of value, money leaving fiat rails, systems that keep working when their operators fail) share a dependency nobody names: the holder has to be able to reach the token. ERC-8426 is the layer we built for that. Five points. 2/ Tokens become accessible Holding an onchain asset today takes a wallet app or a browser extension, a seed phrase, and signing prompts full of hex. Every tokenized dollar, stock or ETH position inherits that funnel. ERC-8426 puts the token on a surface that is already installed on the phone: Apple Wallet and Google Wallet. 3/ ERC-721 in Apple Wallet and Google Wallet interface IERC721WalletPass { // ERC-165: 0xef5f1e71 event PassUpdate(uint256 indexed tokenId); event BatchPassUpdate(uint256 fromTokenId, uint256 toTokenId); function passURI(uint256 tokenId) external view returns (string memory); } passURI works like tokenURI. It resolves to a manifest that holds one acquisition URL per platform: { "version": 1, "formats": { "apple": "https://issuer.example/passes/c3f1.../card.pkpass", "google": "pay.google.com/gp/v/save/eyJ…..." }, "updatedAt": 1754500000 } 4/ The card follows the chain PassUpdate tells the pass issuer to regenerate the pass and push it to devices. It is a separate event from ERC-4906 because pass content changes when metadata does not: a balance, a countdown, a level. The issuer pushes through APNs or the Google Wallet API, and the card on the lock screen tracks chain state without the holder opening anything. 5/ Transactions start from the wallet A pass can carry action links. The holder taps one, the issuer verifies the request, and a state-changing transaction goes onchain. There is no dapp, no browser wallet and no signing popup. Pocket Pad runs this today on Robinhood Chain: tap the card, water() executes through a relayer, and the holder signs nothing. 6/ Why that is safe A pass is a bearer artifact: it can be forwarded, screenshotted and installed on any number of devices. ERC-8426 never takes the artifact itself as authorization. Every state change reachable from a pass needs two checks: proof of control of the owning account, which closes forwarding a fresh ownerOf read at request time, never skipped, which closes the transfer window A product without per-action signatures may use a capability URL in place of check 1, but only if the URL: cannot transfer, burn or approve the token cannot grant standing authority has a bounded, documented effect rotates when the owner asks A GET on a capability URL never acts. 7/ No download, seed phrase, password, app or extension The standard is written for email-onboarded holders. The control proof accepts three kinds of signature: an EOA signature an ERC-1271 contract account ERC-6492, for a counterfactual account that has not been deployed yet ERC-6492 matters because an email-onboarded account often exists only as a deterministic address until its first transaction. An embedded signer meets the check without ever showing the holder key material. In practice the flow is: email, a one-time code, Add to Apple Wallet. The wallet app was already on the phone. 8/ A token can advertise itself Before ERC-8426, a token’s wallet pass was invisible outside its issuer’s own site. Now any client can find it with two reads: const supported = await client.readContract({ address, abi, functionName: "supportsInterface", args: ["0xef5f1e71"], }); const uri = await client.readContract({ address, abi, functionName: "passURI", args: [tokenId] }); const manifest = await fetch(uri).then((r) => r.json()); // manifest.formats.apple, manifest.formats.google A wallet app, a marketplace, an indexer, an email service or a point of sale can offer Add to Apple Wallet for any conforming token. In the public configuration, a metadata-only consumer can read the same manifest from a wallet_pass property in tokenURI. 9/ Discovery you can verify Advertising only works if clients can trust what they find. The optional IERC721WalletPassIssuer (0x470be7e9) lets a contract commit onchain to the Apple teamIdentifier/passTypeIdentifier and the Google issuerId that sign its passes. A client compares that commitment with the manifest’s issuer and with the pass signer, and refuses on a mismatch. A compromised endpoint cannot get its passes installed by a client that checks. 10/ Why the rest depends on this ETH as a programmable store of value needs portability and verifiability where the holder is. Money leaving fiat rails needs to land where people already keep their cards. Resilience needs a holder surface that does not become the new single point of failure. Without a standard way for a token to advertise its pass, each of these is a private integration that works on one issuer’s site. With ERC-8426 the token carries the capability itself, and any client can use it. Everything on that list composes only because of this layer.
1
3
115
Always better in my google wallet
Replying to @huntclubhero
TLDR, ETH GUD TOKENS GUD ALWAYS BETTER IN UR APPLE WALLET
1
33
ignore 🥶 retweeted
This week’s tokenization posts (ETH as a programmable store of value, money leaving fiat rails, systems that keep working when their operators fail) share a dependency nobody names: the holder has to be able to reach the token. ERC-8426 is the layer we built for that. Five points. 2/ Tokens become accessible Holding an onchain asset today takes a wallet app or a browser extension, a seed phrase, and signing prompts full of hex. Every tokenized dollar, stock or ETH position inherits that funnel. ERC-8426 puts the token on a surface that is already installed on the phone: Apple Wallet and Google Wallet. 3/ ERC-721 in Apple Wallet and Google Wallet interface IERC721WalletPass { // ERC-165: 0xef5f1e71 event PassUpdate(uint256 indexed tokenId); event BatchPassUpdate(uint256 fromTokenId, uint256 toTokenId); function passURI(uint256 tokenId) external view returns (string memory); } passURI works like tokenURI. It resolves to a manifest that holds one acquisition URL per platform: { "version": 1, "formats": { "apple": "https://issuer.example/passes/c3f1.../card.pkpass", "google": "pay.google.com/gp/v/save/eyJ…..." }, "updatedAt": 1754500000 } 4/ The card follows the chain PassUpdate tells the pass issuer to regenerate the pass and push it to devices. It is a separate event from ERC-4906 because pass content changes when metadata does not: a balance, a countdown, a level. The issuer pushes through APNs or the Google Wallet API, and the card on the lock screen tracks chain state without the holder opening anything. 5/ Transactions start from the wallet A pass can carry action links. The holder taps one, the issuer verifies the request, and a state-changing transaction goes onchain. There is no dapp, no browser wallet and no signing popup. Pocket Pad runs this today on Robinhood Chain: tap the card, water() executes through a relayer, and the holder signs nothing. 6/ Why that is safe A pass is a bearer artifact: it can be forwarded, screenshotted and installed on any number of devices. ERC-8426 never takes the artifact itself as authorization. Every state change reachable from a pass needs two checks: proof of control of the owning account, which closes forwarding a fresh ownerOf read at request time, never skipped, which closes the transfer window A product without per-action signatures may use a capability URL in place of check 1, but only if the URL: cannot transfer, burn or approve the token cannot grant standing authority has a bounded, documented effect rotates when the owner asks A GET on a capability URL never acts. 7/ No download, seed phrase, password, app or extension The standard is written for email-onboarded holders. The control proof accepts three kinds of signature: an EOA signature an ERC-1271 contract account ERC-6492, for a counterfactual account that has not been deployed yet ERC-6492 matters because an email-onboarded account often exists only as a deterministic address until its first transaction. An embedded signer meets the check without ever showing the holder key material. In practice the flow is: email, a one-time code, Add to Apple Wallet. The wallet app was already on the phone. 8/ A token can advertise itself Before ERC-8426, a token’s wallet pass was invisible outside its issuer’s own site. Now any client can find it with two reads: const supported = await client.readContract({ address, abi, functionName: "supportsInterface", args: ["0xef5f1e71"], }); const uri = await client.readContract({ address, abi, functionName: "passURI", args: [tokenId] }); const manifest = await fetch(uri).then((r) => r.json()); // manifest.formats.apple, manifest.formats.google A wallet app, a marketplace, an indexer, an email service or a point of sale can offer Add to Apple Wallet for any conforming token. In the public configuration, a metadata-only consumer can read the same manifest from a wallet_pass property in tokenURI. 9/ Discovery you can verify Advertising only works if clients can trust what they find. The optional IERC721WalletPassIssuer (0x470be7e9) lets a contract commit onchain to the Apple teamIdentifier/passTypeIdentifier and the Google issuerId that sign its passes. A client compares that commitment with the manifest’s issuer and with the pass signer, and refuses on a mismatch. A compromised endpoint cannot get its passes installed by a client that checks. 10/ Why the rest depends on this ETH as a programmable store of value needs portability and verifiability where the holder is. Money leaving fiat rails needs to land where people already keep their cards. Resilience needs a holder surface that does not become the new single point of failure. Without a standard way for a token to advertise its pass, each of these is a private integration that works on one issuer’s site. With ERC-8426 the token carries the capability itself, and any client can use it. Everything on that list composes only because of this layer.
17
19
2
76
2,339
Went to water it today and actually gasped. When did you get this huge?! Love my little bonsai! 🌱
3
2
11
213
ignore 🥶 retweeted
𝚂𝚙𝚊𝚌𝚎𝚛𝚣 𝚝𝚊𝚔𝚒𝚗𝚐 𝚌𝚘𝚗𝚝𝚛𝚘𝚕. 𝚆𝚎 𝚠𝚒𝚕𝚕 𝚝𝚊𝚔𝚎 𝚘𝚟𝚎𝚛 𝚝𝚑𝚎 𝚞𝚗𝚒𝚟𝚎𝚛𝚜𝚎. 𝙹𝚘𝚒𝚗 𝚘𝚞𝚛 𝚎𝚡𝚙𝚎𝚍𝚒𝚝𝚒𝚘𝚗 👾
680
699
78
1,107
18,055
ignore 🥶 retweeted
You can't stop us @zkunnamed
55
15
1
117
1,748
ignore 🥶 retweeted
GM, my days are more relaxed now haha, waiting for my request to be approved by @SpacerzNFT while watering my plants on @pocketpad_io I don't know if it will be accepted or not for GTD, but I will still water it every day. Ty @huntclubhero
🤖 Made with AI
2
2
8
206
GM, my days are more relaxed now haha, waiting for my request to be approved by @SpacerzNFT while watering my plants on @pocketpad_io I don't know if it will be accepted or not for GTD, but I will still water it every day. Ty @huntclubhero
🤖 Made with AI
2
2
8
206
ignore 🥶 retweeted
Are u kidding me??? Just tried placing an offer, that shit was the easiest experience in web3 I’ve had. Naa @pocketpad_io will go places, just a matter of time..
For the first time ever, bid on pocketpad.io with one tap. Rescind with one more. No wrap and unwrap. No signatures. No more waiting. Welcome to simple crypto.
2
5
13
317
And came back 15 minutes later hahahahahahahaha
27
We can't delay any longer, let's fight with all our hearts, have you secured GTD?
𝚂𝚙𝚊𝚌𝚎𝚛𝚣 𝚝𝚊𝚔𝚒𝚗𝚐 𝚌𝚘𝚗𝚝𝚛𝚘𝚕. 𝚆𝚎 𝚠𝚒𝚕𝚕 𝚝𝚊𝚔𝚎 𝚘𝚟𝚎𝚛 𝚝𝚑𝚎 𝚞𝚗𝚒𝚟𝚎𝚛𝚜𝚎. 𝙹𝚘𝚒𝚗 𝚘𝚞𝚛 𝚎𝚡𝚙𝚎𝚍𝚒𝚝𝚒𝚘𝚗 👾
19
Dont miss the expedition
𝚂𝚙𝚊𝚌𝚎𝚛𝚣 𝚝𝚊𝚔𝚒𝚗𝚐 𝚌𝚘𝚗𝚝𝚛𝚘𝚕. 𝚆𝚎 𝚠𝚒𝚕𝚕 𝚝𝚊𝚔𝚎 𝚘𝚟𝚎𝚛 𝚝𝚑𝚎 𝚞𝚗𝚒𝚟𝚎𝚛𝚜𝚎. 𝙹𝚘𝚒𝚗 𝚘𝚞𝚛 𝚎𝚡𝚙𝚎𝚍𝚒𝚝𝚒𝚘𝚗 👾
21
ignore 🥶 retweeted
i don't think people really understand yet what is being built (let alone what is possible in the future) with ERC 8426 and @pocketpad_io. 1/ the summation of this new protocol is that we have been onboarding and exposing people to digital assets in a way that only those with a high tolerance for friction can get behind... 8426 now unlocks the ability for anyone to buy and interact with these assets directly in their apple/google wallets directly on their phones. these assets have embedded action buttons directly in those wallet cards - for the pocket plant cards you can water your plants, join the holder chat, and play the limited time game Seed Toss. 2/ this version of the ERC is essentially a demo and @huntclubhero (the original 8426 author) is pushing the limits, learning what else is truly possible and enabling others to continue innovating on the foundation he has created. the possibilities are truly endless.. ticketing, verifiable ID etc. all come to mind right away, but as I do more research on what could be possible here as I try to figure out what i want to build on 8426, i think we are going to see entire economic systems overhauled using this tech.. being able to have gasless, signatureless, one click onchain actions directly in your apple/google wallets is a crazy unlock. 3/ i think these being the foundational assets for this entire new standard is something that should not be overlooked. @huntclubhero has made it clear several times that he will drive as much value to the seeds/plants/spirits as possible and i feel like you just can't go wrong stacking pocket assets at this stage and price. there are so many things that can go right here and i am paying very close attention and scooping seeds and watering my plants like they are my digital children, do what you choose, but thats what im doing because i see the vision and want to see crypto meet the average person where they actually already are.
3
9
25
806
When you bid in on an nft, how does the process actually work? Say you want to bid in ETH. First, you open MetaMask and enter the amount you want to wrap. Then you confirm a transaction or two. Then you confirm another one to place the bid. And if you don’t win the collectible? You have to unwrap your ETH, which means confirming even more transactions. It’s 2026, and this is still the standard for bidding onchain. That’s not how people bid in the real world. They fund their account, place a bid, and see what happens. On the Pocket Pad marketplace, you can already buy with a single click. Now you can place offers with a single click too. We’re tearing down barriers that have stood for far too long. Make one offer on Pocket Pad and feel the difference for yourself. Welcome to the future of simple crypto.
For the first time ever, bid on pocketpad.io with one tap. Rescind with one more. No wrap and unwrap. No signatures. No more waiting. Welcome to simple crypto.
19
23
1
96
2,254