Content
@
https://warpcast.com/~/channel/base-builds
0 reply
0 recast
0 reaction
tmo.basin | ensurance agent
@tmoindustries
This week I built.... a script thats checks and returns a full list of any NFT collection's /tokenbound 0x TBA addresses along with owner, token Id, token name, and if owner is EOA or multi-sig we use this for /basin protocol https://github.com/basin-global/Situs-Protocol-Contracts/tree/main/Tools/getAccountData
3 replies
1 recast
4 reactions
tmo.basin | ensurance agent
@tmoindustries
@w @abram this 👆 is kind of where I was/am headed with 👇 https://warpcast.com/tmo.eth/0xde1664f0
1 reply
1 recast
0 reaction
tmo.basin | ensurance agent
@tmoindustries
we have this "send tokens" to account name (w.situs, w.basin etc) built into our app but would much rather see it at the smart account level i.e. to @abram
1 reply
0 recast
0 reaction
tmo.basin | ensurance agent
@tmoindustries
👆👇 queries ownerOf. We are adding option to send to TBA also. The toggle would either send to ownerOf 8bram.basin OR send to the TBA 0x of 8bram.basin which is 0x0ef58Cfe78bf137e006c8E72C914cfa72EB4CB55 👇
1 reply
0 recast
0 reaction
tmo.basin | ensurance agent
@tmoindustries
but instead, this could all be done at the smart account level by entering the .basin 721 0x into address book - address book script queries the contract for the needed data (I suspect this is how the FC send works) 👇 @abram @w
1 reply
0 recast
0 reaction
tmo.basin | ensurance agent
@tmoindustries
each smart account can add collection level 721 0x's they want to have in address book. script does all the work. imagine adding the @ensdomains 721 0x like you did with @farcaster .... now all ENS names are in your 'address book' - logic also grabs TBA 0x - toggle send to OwnerOf or TBA!!!
0 reply
0 recast
0 reaction
