Shyft Network

[ update Jul 1, 2021 4:51PM EST ]

We’ve found another minor glitch that will result in a “success” transaction but no upgrade event.

This will not affect the total balance or prevent you from any other activities. This will consume gas much like a failed transaction.

Our diagnostic

We have found that the issue relates to our upgrade.shyft.network dApp’s rounding of floating point numbers in comparison to the input fields (human readable) and the ‘wei’ value in the background.

We can see this in the first completed Upgrade that emits Logs and Events. The second has not completed, the transaction is a ‘success’, but no on-chain balances have changed, and no event logs etc.

Zooming in, we can see that the input value ends with ‘050000’ and the ‘Quantity’ of the actual tokens in storage in this address are ‘048192’. As the input value is higher than the actual value, the Upgrade event fails, and due to the fact that we could not modify the original contract, we could not get additional events/notifications in place.

Suggested Fixes

1. A bit more patience — We’ll get a new dApp up that does the mathematics properly in relation to the input fields, should be able to get it up later tonight, reasonable 100% estimate is Friday June 2nd at 5pm EST.

2. If you want to do it right now — Simply enter the number manually into the text field instead of using the ‘max’ button on the interface, round to the nearest 5th decimal and you’ll be perfectly fine in consideration of the 0.0001 SHFT sent to all previous Holders.

Thanks for the feedback and support. We are working together to get this phase over as quickly as possible.

[ update Jul, 1, 2021 ]

The Shyft co-founder team came together to problem solve, and we’ve found a clever fix for this issue!

We ended up using https://disperse.app to send 0.0001 SHFT to each user, forcing Etherscan to update the token balances & associations for each of the existing token holders from the Shyft v1 contract.

We did this by using “export as csv” from the token holders in the v1 (https://etherscan.io/token/0xcba3eae7f55d0f423af43cc85e67ab0fbf87b61c#balances)

and sent out the 0.0001 SHFT to each existing token holder, across the board.

We appreciate the community’s patience & feedback while we were inspecting this issue :)

Hello everyone, Chris from the Shyft Network here. We’ve discovered some tooling intricacies brought on by our token upgrade process that may be causing some concern if you, the user, are trying to confirm your balances using multiple sources.

NOTE: If you haven’t tried to do the token upgrade, read this first.

Description / What to Look For

Here we have an example of the “Events” of the v2 upgraded SHFT contract (0xb17…D85):

https://etherscan.io/address/0xb17C88bDA07D28B3838E0c1dE6a30eAfBCF52D85#events

As we can see, this user (0x6153…213) has completed an upgrade for 3959…0000 tokens. This value is in “wei”, with 18 decimals of precision.

At this point, even though we can see that the user has Upgraded 396.90316283213986 SHFT tokens successfully, Etherscan will (currently) not report this amount for the user (0x6153…213).

We can see that this user is not reflected in the Token page at the moment:

And on this user’s account page, the SHFT [ Wrapped ] token isn’t appearing yet.

Issue Severity: (#004, 2/10) — interfaces, user expectations, non-critical, important

Cause

Etherscan does not read the custom ERC223-style receipts for the “TransferFromBip32X” event, and so does not automatically create/associate their user’s page with the Token.

Solutions

1. Don’t Panic

Here is one example of a metamask wallet with both of the SHFT tokens included. The icon we’re interested about for the results of this Upgrade event is the one that looks like what I’d call an “orange mountain”

[ ex 1 & 2 ]

After the v2 Upgrade event, you will see your tokens in metamask!

2. If you really need to see it on Etherscan, you can help yourself

Use MetaMask to send a single v2 SHFT to yourself. This will immediately update your balance to the totality of the amount of v2 SHFT you own, as well as adding your address to the etherscan.io ‘holders’

3. And if that’s too complex, we can help you too!

Just DM us on Telegram and we’ll help you out within 48 hours, we’re here for you and will respond as soon as we’re able.

4. Patience until tools are updated.

All of your tools are our tools as well. Etherscan’s 100% compatibility and user-friendly-ness are important to us.

We’re in communication with the Etherscan team to utilize our events to incorporate our flow of the holders/balances in relation.