Thread by @krippenreiter

[1/🧵] An easy step-by-step guide for utilizing a #Ledger hardware wallet to configure @BifrostWallet as an #autoclaim executor on the #Songbird (#SGB) network.

To learn more, keep on reading and complete the steps. (😅 Warning: paranoia ahead.) 🧵👇

[2/20] — What is the primary goal? —

The basic purpose of an executor address is to claim rewards on your behalf in order to save time, max. compound interest, & reduce unwanted exposure of a cold wallet.

Executors will then use auto. claiming to route rewards to your acc. 👍

[3/20] — 1⃣ Is it safe to assign the task to an executor? —

The executor cannot claim to any address other than the one provided by the user, therefore automatic claiming is secure. 💪
. . .

[4/20] — 2⃣ Is it safe to assign the task to an executor? —

It is also trustless (no trust is required) since it is controlled by a smart contract rather than the executor itself.

🧐 To recap, the executor cannot steal your funds or send it to another person's wallet ❗️

[5/20] — ℹ️ — 1⃣ Hardware Wallet Fundamentals —

🔸 Your only (❗️) source of truth is w/e is displayed on your hardware wallet's display, NOT what is displayed on your laptop screen

🔸 Nothing on your laptop matters as long as the TX has not yet been signed w/ your HW-wallet

[6/20] — ℹ️ — 2⃣ Hardware Wallet Fundamentals —

📣 Repeat after me:

😤 I will never, ever write my 12, 24, or 25 SEED online, write it into any software that demands it, or expose it to anybody or anything.

[7/20] — 1⃣ @FlareNetworks Portal —

There are several options here, and you may select whatever executor you want.

In this case, we'll use:
🔸 portal.flare.network

And use the @BifrostWallet's exec. address as our executor:
🔸 0xdD76d702358936Af39c0E9F7E71F9512C83cacaE

[8/20] — 2⃣ Am i hacked? —

As soon as you approve the addition of the executor's address, an MM notification will appear w/ a completely new address, requesting that you sign.

⚠️ If your alarm bells went off, that's perfect!

But, everything is OK in this scenario. 😅

[9/20] — 3⃣ To sign or not to sign —

The new address is the "#ClaimSetupManager," which is the smart contract we will trust.

The executor address, which we intended to include in the first place, may be found inside the HEX data.

[10/20] — 4⃣ Use your hardware wallet to sign —

After you accept the MM notification pop-up, your hardware wallet will prompt you to sign the transaction.

❗️ BEFORE you do so, browse the "View on block explorer" MM URL in the #SGB Explorer and pose questions:
. . .

[11/20] — 5⃣ Pose Questions —

Examine the HW's display:
🔸 Am I even signing a #SGB network TX?
🔸 Does the "#ClaimSetupManager" Contract-Address you opened in the explorer match the address displayed on your hardware wallet's display?
🔸 Are the fees in SGB as expected?

[12/20] — 6⃣ Examine the blockchain —

You had just signed a TX on #Songbird (#SGB) with your HW's #privatekey, but there was no way to verify that the HEX data had not been tampered with.

Let us now search for the validated transaction and the HEX data.
. . .

[13/20] — 7⃣ Examine the Contract Call —

Open the #Songbird Explorer again, but this time browse your own #SGB address and click on the last transaction hash that says "#SetClaimExecution."

It will take you "behind the scenes" of what occurred as you signed the TX. 🧐

[14/20] — 8⃣ Examine the HEX data —

📝 In layman's terms, what you're seeing is that your account has approved that the executor (@BifrostWallet), as specified in the "Raw input" data field, is now delegated to claim on your behalf & that all unclaimed funds will be sent to you.

[15/20] — 9⃣ The last check —

Make sure you understand what you just did, & double-check the following:
🔸 The "#ClaimSetupManager" address was the one you knew, & it is also included in the "#FlareContractRegistry"
🔸 Your TX's "Raw Input" displays the right executor address.

[16/20] — 🔟 Undo everything —

If you wish to undo assigning the right to the exec. to claim on your behalf, just repeat everything, but this time insert an empty address as the executor.

This will undo the smart contract's ability to listen to the executor on your behalf.

[17/20] — #Code Repository —

If you want to read the "#ClaimSetupManager" code first, here it is:
🔗 gitlab.com/flarenetwork/f…

[18/20] — TL;DR —

1⃣ Make certain that you only sign a transaction for the right address connected with the "#ClaimSetupManager" listed in the "#FlareContractRegistry".

2⃣ Before and after signing the TX, double-check that the HEX data includes the right executor address.

[19/20] — ⚠️ Fake Supports ⚠️ —

⚠️ Never communicate with any wallet or blockchain support accounts on Twitter.

It's not worth the risk because there are barely 0.1% legitimate ones.

Just don't, under any circumstances, write with them in DMs or click any URLs.

[20/20] I hope you enjoyed this detailed step-by-step tutorial that walks you through the process and shows you what to look for and what not to look for. 😅

Please follow me here:
@krippenreiter ☀️

Feel free to contribute by sharing here: 👇❤️

https://twitter.com/krippenreiter/status/1650324365454585856?s=20

@threadreaderapp unroll