Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For October 2018 #146

Closed
flix1 opened this issue Oct 29, 2018 · 6 comments
Closed

For October 2018 #146

flix1 opened this issue Oct 29, 2018 · 6 comments
Assignees

Comments

@flix1
Copy link
Member

flix1 commented Oct 29, 2018

Summary

  • BSQ requested: 500
  • BSQ address: B18pxrZRFJ7Q1PsND9xqayk1uQbtZiH39MC

Contributions delivered

Roles performed

@flix1 flix1 changed the title For October 2018 WIP For October 2018 Oct 29, 2018
@ripcurlx
Copy link
Contributor

@flix1 Just to be sure: Did you use a new Bisq address by intent? Before you used always B1Pdq17bL5GiitCsNybi3Fc3V8qa7btYnPe

@flix1
Copy link
Member Author

flix1 commented Oct 31, 2018

@ripcurlx actually I wanted to ask about that... B1Pdq17bL5GiitCsNybi3Fc3V8qa7btYnPe was my previous BSQ address. However if I hit Ctr+D now and go to the DAO section I see this new address B18pxrZRFJ7Q1PsND9xqayk1uQbtZiH39MC. This happened since the update to v. 0.8.0.

I'm hoping that my recovery seed will allow me to still have access to the old address... can you please confirm that?

image

@ripcurlx
Copy link
Contributor

@flix1 I think atm I could just change your old address to match the new one you have access to as long as we are not on Mainnet. @ManfredKarrer Or do I miss something?

@flix1
Copy link
Member Author

flix1 commented Oct 31, 2018

Thanks!
Obviously once we are on Mainnet making sure to back-up everything will be as important as it is in Bitcoin.

@ManfredKarrer
Copy link

The current address is not important and many have lost their old wallet. So i will request before mainnet anyway an new address from all... so no its just an ID.

@ripcurlx
Copy link
Contributor

ripcurlx commented Nov 4, 2018

Closing as complete, see #149 (comment).

@ripcurlx ripcurlx closed this as completed Nov 4, 2018
@flix1 flix1 mentioned this issue Mar 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants