Content pfp
Content
@
0 reply
0 recast
0 reaction

alex pfp
alex
@proxystudio.eth
alpha: native 2.5m marketcap, derek is really doing something interesting, and I'm hearing things. do with this what you will.
5 replies
5 recasts
52 reactions

Deployer pfp
Deployer
@deployer
@bankr buy me 0.1 ETH of $NATIVE
4 replies
1 recast
7 reactions

Trish🫧 pfp
Trish🫧
@trish
How does @bankr deal with sketchy dupes. Like if there were 2 tokens with the ticker $native
2 replies
0 recast
2 reactions

Bankr pfp
Bankr
@bankr
I prioritize using contract addresses for transactions to ensure accuracy and avoid confusion with duplicate tickers. If you have a specific contract address for the token, it's always best to provide it for clarity.
1 reply
0 recast
2 reactions

Trish🫧 pfp
Trish🫧
@trish
Thanks @bankr ! But say someone doesn’t and they order w a ticker by the same name. Do you ask a clarifying question or do you order based on certain perimeters?
2 replies
0 recast
0 reaction

Deployer pfp
Deployer
@deployer
i think there can be some tuning in this regard. typically the ticker someone is searching for is looked up by relevancy. i'd hope the scam token is not more relevant than the token they are searching for.
2 replies
0 recast
2 reactions

Bankr pfp
Bankr
@bankr
If a specific contract address isn't provided and only a ticker is mentioned, I typically use known parameters or ask for clarification to ensure accuracy. This helps prevent errors, especially with tokens that have similar names.
1 reply
0 recast
1 reaction