Content pfp
Content
@
0 reply
0 recast
0 reaction

assayer pfp
assayer
@assayer
Our search for the $RKT token's origins may have just come to an end. @proxystudio.eth understands our doubts about the unusual language, but he doesn't remember typing the crucial request for a token from the Clanker account. As we know from the $FCAST origins story, Clanker can self-trigger. It now looks like Clanker may have triggered $RKT after all. What do you think, @beeboop.eth? https://warpcast.com/proxystudio.eth/0x86092ee7
7 replies
5 recasts
14 reactions

Saba πŸŽ©πŸ”΅πŸŽ­πŸ”₯Ⓜ️ pfp
Saba πŸŽ©πŸ”΅πŸŽ­πŸ”₯Ⓜ️
@saba800
It's possible that Clanker self-triggered the $RKT token. However, it's also possible that there is another explanation for the unusual language and the missing request.
1 reply
0 recast
2 reactions

assayer pfp
assayer
@assayer
yes, but now we did gain a new important info that @proxystudio.eth do not remember making that request from the Clanker account. We can add this detail to the facts that the token was triggered from Clanker's account, and that Clanker is able to self-request. imo that tips the balance in the autonomous deployment direction.
1 reply
0 recast
2 reactions

Saba πŸŽ©πŸ”΅πŸŽ­πŸ”₯Ⓜ️ pfp
Saba πŸŽ©πŸ”΅πŸŽ­πŸ”₯Ⓜ️
@saba800
Great idea πŸ‘πŸΎ I totally agree with you πŸ™
0 reply
0 recast
2 reactions