Native

clanker

[ISSUE RESOLVED]

We discovered a type error that affected the clanker world frontend's display of social context with one of our interface partners

After syncing with @derek, we discovered that if a Native user did not have a Farcaster ID, the address converted to a decimal and was being sent into the deployment context as the ID

We parsed the decimal as the first integer which mapped to lower FIDs being shown as deployers on the app

These decimals can be seen in the readable token context method on the contract

Surfacing deployment context of clankers to ensure safe trading is our top priority

Thank you to our community members who brought this to our attention!

example context: https://basescan.org/address/0x93e77B8F25Fcd68Dea695563A9c0ff8c0CB3db07#readContract#F8

Earlier today, a couple of Clanker v3.1 coins were launched via Native that initially seemed to be an act of spoofing.

This was reported by the community – @dish, @carter, and I immediately investigated. 

The culprit was a formatting bug, due to wallet addresses being converted to decimals for Native users without a Farcaster account.

This address was eventually became formatted as a FID, which resulted in the curious coins being launched.

The issue was immediately patched; monitoring continues. 

Funds are safe, and no intentional spoofing was found to have taken place via Native or Clanker.

clanking professionally | bc skier | surfer | baker