Self Flow Team Testing

[ori-near]

No description provided.

[petersalomonsen]

@ori-near @frol We talked about how to test the self creation flow and be able to delete the sputnikdao contract when done, and get the deposited funds in return.

Suggestions are:

1. Deploy a sputnik-dao factory contract that creates the sputnikdao contract with the keys of the transaction signer. This way the initiator of the instance deployment can delete the account and get the funds in return.
2. Set up the self-creation flow on testnet

If we go for alternative 1, we could also offer this to other users that just want to test-run the treasury-dashboard.

Alternative 2. would take more effort than number 1, and I'm also not sure if we have all the dependencies such as the linkdrop contract.

[frol]

I would go with (1) as (2) will require to setup (1) on testnet and additionally do even more stuff there. Let me know if you need NEAR to cover the setup.

[petersalomonsen]

I would go with (1) as (2) will require to setup (1) on testnet and additionally do even more stuff there. Let me know if you need NEAR to cover the setup.

Added #190

[petersalomonsen]

I would go with (1) as (2) will require to setup (1) on testnet and additionally do even more stuff there. Let me know if you need NEAR to cover the setup.

In the sputnikdao-factory docs, there is an option to provide a public key. It does not seem to be implemented though, so I've done the implementation here: near-daos/sputnik-dao-contract#208

[petersalomonsen]

Also, just want to mention that I noticed the comment here, where using a self-upgrade proposal with a contract that can delete the account is a method that is already supported. We should consider this option too.