With the US geo-blocked from the official ApeCoin staking site, many will find themselves interacting with the contract through Etherscan directly for the first time.
Here's everything you need to know in order to successfully stake your ApeCoin through Etherscan 1/🧵
2/ Staking through Etherscan is clunky, but you benefit from full control and a better understanding of what you're doing - like driving with a manual transmission.
The first thing you'll want to do is head to the ApeCoin contract and connect your wallet: etherscan.io/address/0x4d22…
3/ We need to give the staking contract spend permission. It is easiest to grant the maximum integer value, so you never need to re-approve.
spender: 0x5954aB967Bc958940b7EB73ee84797Dc8a2AFbb9
amount: 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
4/ Next, we head to the staking contract and connect the same way we did for ApeCoin.
That contract is here: etherscan.io/address/0x5954…
Once connected, next steps depend on which pool you want to use
- ApeCoin only
- BAYC
- MAYC
- BAKC (paired)
Let's go through them 👇
5/ ApeCoin only has two options: deposit on behalf of somebody else, or (what most people will probably use) deposit to your own staking position.
To deposit to your own position, simply paste the amount you're looking to deposit, hit "write", and confirm the transaction.
6/ Quick aside: It's important to note that ApeCoin has 18 decimal places, so the _amount you're depositing should be (number of ApeCoins * 10 ^ 18).
If you're depositing your full balance, you can save yourself the calculation by pulling it from the ApeCoin contract
7/ If you ever want to withdraw or claim your rewards, the process is similar. You can claim to your own address, or specify a recipient.
8/ If you want to deposit to a BAYC or MAYC pool, you'll need to provide a token ID. Don't worry, your NFT get transferred or approved in the process. The function simply verifies ownership.
Here is the proper input to deposit token ID 8903, along with the max ApeCoin.
9/ Note the double quotes, your tx will fail if you don't include them.
You can commit multiple BAYC or MAYC in a single transaction as long as each has at least 1 ApeCoin tied to it. Here's an example of the input to commit 2 (you can extrapolate from there)
10/ Withdrawals are mirror images of deposits for these if you use the "Self" variants. If not, the only difference is that you can specific a recipient for the withdrawn ApeCoin.
IMPORTANT: THE POSITION IS OWNED BY THE OWNER OF THE APE. SELL THE APE, SELL THE POSITION.
11/ On to BAKC pairs, which get a little trickier. BAYC + BAKC pairs go in the top box, MAYC + BAKC in the bottom box. If you don't have one or the other, an empty array ([]) is required.
The first ID here is the ape, the second is the kennel, then the amount of ApeCoin.
12/ And again, the withdraw is the same format.
13/ Some notes:
As seen below, depositing *only* verifies ownership if the committed NFT or NFT pair has no staked balance. Once a stake is set up, anybody can add to it. Useful for topping up if you have $ape in other accounts!
14/ We are going to see a rise in losses over the next few months. I see two main scenarios:
15/ Accidental
User A sells their ape to User B and doesn't realize that the stake position goes with it. User B now owns all of the deposited ApeCoin.
16/ Malicious
Scammers request pool withdrawals (instead of approvals or seaport signatures). These will be less recognizable to the average user, and many may forfeit their staked ape to phishing schemes.
17/ We're going to see a TON of ApeCoin interfaces pop up. They will obfuscate this manual work away from you, which is great but ONLY if you trust them not to manipulate it. Stick with the ones that you trust, or when in doubt, just use Etherscan and input the data yourself
18/ I hope you've found this thread helpful.
This is part of a much larger series where I'll be breaking down the different options for staking interfaces and functionality.
If you enjoyed it, please retweet the opening thread!
19/ tl;dr Etherscan requires the most manual work out of the frontend options out there, but it also requires the least amount of trust.
I would recommend it for the more tech savvy, or those looking to learn.
Ease of Use - 5/10
Safety - 9/10
Additional Functionality - 1/10
20/ For a more code-focused review on the contract, check out @0xCygaar's helpful thread from earlier today:
An addendum on checking your unclaimed rewards
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.