One time change of TECH addresses (as requested by owner because access was lost or another reason)

There might be people joining the TEC who have never even used a wallet. With the steep learning curve, there’s bound to be mistakes/accidents. This would help those people.

There could be people who take advantage of the knowledge of someone’s lack of experience with wallets etc and convince them to transfer the tokens to them instead so they can ‘do the technical/confusing stuff’ for them. How can we make sure the person doing the address change is not being taken advantage of?

What if the trusted parties end up being really busy? Does it affect anyone negatively to have to wait to change addresses?

2 Likes

I concur.

When I was signing up to be a trusted seed I read somewhere (from a prompt) that some folx set up another wallet for this…I took that as a cue to make another. While I don’t need my address change I can imagine some folx may be wanting to transition back to thier original wallet address.

2 Likes

I was waiting until further discussion from the community happened before expressing my opinion on this matter. I don’t really like the idea since as @natesuits says it could be open to abuse.
I understand people might be newcomers, however web3 addresses are as delicate as identities themselves (even more in the future). I think all of us realize about this as we continue to grow in the space and we’re not exempted to make these mistakes.
Identity theft is a real threat to people both irl and web3 and I feel it shouldn’t be as easy as “yeah, here are your new TECH tokens”. These would have to be very specific cases if we’re willing to make such an exemption and it should be a one-time-only kind of thing.
Sorry if I’m being the serious, party-pooper guy to bring this up, but I feel some awareness should be brought up with these cases about taking care of private keys, since this could scale to more severe situations.
I trust the community will make the best decision on this, regardless of the outcome.

2 Likes

I agree with you Chuy and remember in order to this, to happen 88% of the voters must support this proposal in order to pass, it would be pretty easy to block it by the community. I also agree hatchers should be more careful with that but at the end of the day we are all humans and things happen and personally I believe that the trusted seed gardeners are going to do a great job checking indentities and making sure everything its all right, they have a curated list and its going to be doble check for all 3. This will probably won’t happen again in the future when TEC addresses are spread around and there is not a curated list of all members.

But in my opinion, if a Hatcher lost his key we can give a hand as a human center community, I personally would feel really bad losing my Hatcher address and if the community helps me with an +88% of voters I would feel so happy. And there are only 273 addresses I feel we can do it, but lets vote, this will be probably the first one!

3 Likes

Vote will be ready in less than 2h! Snapshot

1 Like

I will be voting to support this.

We are all Hatchers. We are all in this together. I would not have any single one of us lose out if we can avoid it. And we can avoid it.

For the concerns raised about abuse, the points made are valid. I acknowledge that but also see that a fair and honest burn/mint can be performed and validated by trusted members of our Community. Specifically because we are all Trusted Seed members. After the Commons upgrade, when the public and enter and exit the TEC via the ABC, that’s a different story. But that is not our current situation. So let’s take care of each other.

This is a Trust but Verify moment, not a Sorry For Your Loss.

5 Likes

We should always put the community before the individual. In this case general sentiment appears to be grant a second chance. Wow, how amazing is it, to be in a community where this is even possible!! Yet this feels ultra-serious. A second chance in the immutable, irreversible world of blockchain is no small thing. Accordingly, imo this should not be freely & easily approved.

But it CAN be approved

They should need to pay a small-mod surcharge into the common pool, or even better, write a thousand word essay on why they want a change, why they believe changes should be allowed, and what they will do to avoid requesting changes in the future. This piece of writing should be shared with the TEC members.

Yes we need to take care of our community 100% I agree. Giving them a second chance in the irreversible world of blockchain should not be taken lightly. Adding a disincentive will reduce abuse of the system. Someday it will be me requesting a reverse…or you…

2 Likes

(proposal with edits integrating feedback)

We are submitting this proposal on Snapshot for signaling. This way we can capture the signalling from the Community without paying the 1000wxDAI tollgate fee. Please feel free to leave feedback on the Forum thread.

If the vote passes on Snapshot, we will make this proposal on the Hatch DAO.

Proposal Title:

One time change of TECH addresses (as requested by owner because access was lost or another reason)

Proposal Information:

Several people have lost their keys or asked to switch their TECH address. As a human centered community we have a vested interest to ensure that our community members retain their voting rights by control of their wallets. We are a value aligned community, committed to nurture the TEC economy in its early stage, while focused on long term success. It is important that everyone in this group has a holding of their tokens and feels comfortable with their address to engage in upcoming decisions.

Note: We recognize that there may be future requests for address changes. Future requests are not covered within the scope of this proposal.

Proposal Details:

Allow a period of time for requests for address changes
Burn TECH in those addresses and remint to specified new addresses
Make request to Commons Stack to burn CSTK in those addresses and remint to specified new addresses
Expected duration or delivery date (if applicable):

Proposed timeline:

Snapshot vote: Sept 2 (for 4 days)
Accepting requests for address changes: now until Sept 15 12pm CET
HatchDAO vote: Sept 16
Burn and minting TECH (Commons Stack will determine timeline for CSTK): Sept 21

To make this request, our community members should contact griff#3281, Dan Knobelsdorf.eth#0326 and Tam2140#9361 for security reasons and (1) share the reason for the change, (2) the old address, and (3) the new address.

Sep 15 griff#3281 will post on the forum thread all the addresses that are going to be burned and the addresses where all those tokens are going to be minted for transparency, if no one opposes the decision it’s going live as stated before on sep 16.

If the community supports this initiative on the snapshot vote we will propose to the Hatch DAO to burn and mint the TECH, and request that Commons Stack does the same for CSTK.

How does this help Token Engineers and benefit the Token Engineering community?

It reinforce our cultural build as a human center DAO

Team Information (For Funding Proposals)

These are the community members that will support and provide the initial funding for the tollgate fee for the Hatch DAO proposal.

Zeptimus
Tamara
Griff
Dan

Funding Information (For Funding Proposals)

1000 wxDAI from the non-redeemable pool in order to cover the tollgate fee

1 Like

from Imgflip Meme Generator

4 Likes

We have THREE TECH holders that have reached out and asked for an address change

We will propose

  1. to burn 2447.046 TECH from
    0xFBC56Be13C23c18B6864D062e413da3c7e0f74Fb
    And mint 2447.046 TECH to
    0xFB074ABA249F6a75edA10996c3EFa6d66465B8b3

  2. to burn 9256.453 TECH from
    0x8D70e8D63BfE565e0fe2CD338ebe05cC7256210c
    And mint 9256.453 TECH to
    0x2dD3d3B07BC822aa9bEF925f06FabaCD23E7022a

  3. We will burn 10572.022 TECH from
    0xB24b54FE5a3ADcB4cb3B27d31B6C7f7E9F6A73a7
    And mint 10572.022 TECH to
    0x5b0f8d8f47e3fdf7ee1c337abca19dbba98524e6

5 Likes

LAST CHANCE IF YOU WANT TO CHANGE YOUR ADDRESS!!!

DM me, Tam, Dan or Zep on Discord, NOW!

5 Likes

There was a difference with 1 address that’s why we got delayed the final addresses are the ones posted before by Griff.

  1. to burn 2447.046 TECH from
    0xFBC56Be13C23c18B6864D062e413da3c7e0f74Fb
    And mint 2447.046 TECH to
    0xFB074ABA249F6a75edA10996c3EFa6d66465B8b3
  2. to burn 9256.453 TECH from
    0x8D70e8D63BfE565e0fe2CD338ebe05cC7256210c
    And mint 9256.453 TECH to
    0x2dD3d3B07BC822aa9bEF925f06FabaCD23E7022a
  3. We will burn 10572.022 TECH from
    0xB24b54FE5a3ADcB4cb3B27d31B6C7f7E9F6A73a7
    And mint 10572.022 TECH to
    0x5b0f8d8f47e3fdf7ee1c337abca19dbba98524e6

Gardeners can confirm this is correct by giving a like to this post when all 3 aproves that sem will make the proposal (we dont have an interface on the hatch DAO )

5 Likes

Confirming these are correct.

3 Likes

This is the EVMcripr script we are using:

exec agent:0 transfer 0xe91D153E0b41518A2Ce8Dd3D7944Fa863463a97d 0xc125218f4df091ee40624784caf7f47b9738086f 1000e18
exec token-manager burn 0xFBC56Be13C23c18B6864D062e413da3c7e0f74Fb 2447.045542334842592122e18
exec token-manager mint 0xFB074ABA249F6a75edA10996c3EFa6d66465B8b3 2447.045542334842592122e18
exec token-manager burn 0x8D70e8D63BfE565e0fe2CD338ebe05cC7256210c 9256.453198232943864182e18
exec token-manager mint 0x2dD3d3B07BC822aa9bEF925f06FabaCD23E7022a 9256.453198232943864182e18
exec token-manager burn 0xB24b54FE5a3ADcB4cb3B27d31B6C7f7E9F6A73a7 10572.021866075814165263e18
exec token-manager mint 0x5b0f8d8f47e3fdf7ee1c337abca19dbba98524e6 10572.021866075814165263e18

The vote gives back the 1000 wxDAI (0xe9..7d) to the vote proposer’s address (0xc12..6f) to pay for the tollgate fee. Then it burns and mints the same amount of TECH tokens, effectively “transferring” all the tokens from the old addresses to the new ones.

5 Likes

The vote is on in the Hatch DAO: Aragon

In the description it says that it’s going to trasfer 1000 * 10^18 wxDAI to an address, but it’s because the parser is not processing the decimals, it’s just 1000 wxDAI.

This is the first official vote of TEC, as well as the first one made with EVMcrispr! :tada:

6 Likes

Interface it’s a bit buggy, if anyone trying to vote and it’s not loading try to press F5 (or shift-refresh, took myself 20 attempts, do not hesitate keep trying! :smiley: ). Make sure to get some xdai to be able to pay the gas (1 xdai should pay your gas like forever :D). And last but not least, do not check the clock it says the vote have 2 days from now, its because blocks are faster on xdai and it bugs the interface, the vote will end in 4 days since Sem posted it yesterday night CET.

4 Likes

:white_check_mark: ¡Todo chévere! Good work y’all!

4 Likes

We forgot to add permissions to mint and burn tokens for the voting app, so we will need to do an extra vote with these commands:

connect 0x4625c2c3E1Bc9323CC1A9dc312F3188e8dE83f42 tollgate.1hive dandelion-voting.1hive
exec agent transfer 0xe91D153E0b41518A2Ce8Dd3D7944Fa863463a97d 0xc125218f4df091ee40624784caf7f47b9738086f 1000e18
grant dandelion-voting.1hive token-manager MINT_ROLE dandelion-voting.1hive
grant dandelion-voting.1hive token-manager BURN_ROLE dandelion-voting.1hive

The vote gives back 1000 wxDAI that are spend on the tollgate fee, and adds permissions to be able to execute the previous vote. The vote is planned for in a few hours, on Wednesday Oct 13th at 0:00 UTC.

4 Likes

The new vote has it’s own thread: Changing permissions on the HatchDAO

1 Like

This vote has been executed on November 3rd 2021.

3 Likes