Author

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 990. (Read 4670673 times)

legendary
Activity: 1512
Merit: 1012
Still wild and free
Hello,
I consider to buy some Monero for the first time and took a look for a good wallet. I am wondering how secure MyMonero.com is? Is it like an exchange where all coin could be stolen without having the private key?

No, it's more like blockchain.info, the private key is only on the client side and never ever known to the website.
tyz
legendary
Activity: 3360
Merit: 1533
Hello,
I consider to buy some Monero for the first time and took a look for a good wallet. I am wondering how secure MyMonero.com is? Is it like an exchange where all coin could be stolen without having the private key?
sr. member
Activity: 341
Merit: 250
Hey Monero Community !!

Can anyone please guide me on how to create a custom Monero burn address, or generally in the Cryptonote protocol?

Will appreciate your kind help.

Create a wallet in a live environment in ram with a super long password (100+ characters) and don't write down it or the seed. Send your coins to the address. Why do you want to burn your coins?

Yeah, I guess I wasn't specific enough.
I'm looking for a way to create a provably unspendable burn address.
Meaning it should be obvious, for example contain a lot of consecutive X's.

keep generating wallets until you get one with a lot of x's.

this vanity address generator exists

https://monerotalk.org/t/vanity-address-generator/134

https://github.com/ehmry/monero-vanity

so you'll essentially publish the viewkey?


The idea is that nobody will have the private key so nobody will have the possibility to spend the funds.

I want to generate an address, to which it's highly improbable anyone will have the private key.

EDIT: Counterparty created such a BTC address back in the days of their launch

Couldn't you still take the same advice I gave but then take whatever address was given and replace the first 10-15 characters with something along the lines of "xxxxxmoneroxxxxx", then again, the viewkey would no longer work so you wouldn't be able to view it anyway. Interesting.


Will this address be valid? will it be possible to send coins to this address? will it be checksum approved?

Even if it did work, it wouldn't serve the purpose because without a viewkey, you can't prove what the address holds. And since the viewkey is derived from the private key, you won't have a valid viewkey.

I think the best course of action would be to somehow provably create a wallet address without ever retaining the files, seed words, and password. Then you'd still have a view key to see the balance but coins could never be spent. Not sure how you overcome the "trust factor".


The idea I thought of is to create 2 addresses, one normally generated address with public viewkey and the other one a burn address without viewkey at all as no one as access to it.
Burn process can be done in 2 steps: send the coins to first wallet and from this one to the burn address.
That way the transactions are visible to the public but no one has access to the receiving address.

Now, I'm not familiar with the Cryptonote checksum rules
Can anyone create an address with as many X's as possible and a valid checksum??
legendary
Activity: 3766
Merit: 5146
Whimsical Pants
I had a post deleted from this thread by a MOD and I do not understand why.

Shortly after Monero was added to shapeshift.io I posted somewhat tongue in cheek and somewhat seriously that doing Dash->XMR conversion was IMO a solid play.  I illustrated this with a screenshot of that functionality on shapeshift.  The image I used is here:

https://i.imgur.com/Yva8Pjv.png

The reason I bring it up here is I am somewhat suspicious of the motivations behind this deletion.

I was not off topic.  I was celebrating the fact Monero was on shapeshift, and I was also stating the fact (I was right by the way) that moving Dash into XMR would be a +EV trade.  I still think it currently is.

I was not trolling or spamming.

I find this action draconian. 
legendary
Activity: 1105
Merit: 1000
Couldn't you still take the same advice I gave but then take whatever address was given and replace the first 10-15 characters with something along the lines of "xxxxxmoneroxxxxx", then again, the viewkey would no longer work so you wouldn't be able to view it anyway. Interesting.


Will this address be valid? will it be possible to send coins to this address? will it be checksum approved?

It'll fail deserialisation.

I don't think it's feasible to create a burn address where you can make the viewkey public but prove that the spend key is unspendable. Maybe a better solution is just to set the unlock time at some ridiculous point in the future, I'm not 100% sure if we even have a rule about max unlock time.

How much work would it be to set up a website for "Monero Tests" (with Javascript). I'd love to host a site like this.
donator
Activity: 1274
Merit: 1060
GetMonero.org / MyMonero.com
Couldn't you still take the same advice I gave but then take whatever address was given and replace the first 10-15 characters with something along the lines of "xxxxxmoneroxxxxx", then again, the viewkey would no longer work so you wouldn't be able to view it anyway. Interesting.


Will this address be valid? will it be possible to send coins to this address? will it be checksum approved?

It'll fail deserialisation.

I don't think it's feasible to create a burn address where you can make the viewkey public but prove that the spend key is unspendable. Maybe a better solution is just to set the unlock time at some ridiculous point in the future, I'm not 100% sure if we even have a rule about max unlock time.
legendary
Activity: 1442
Merit: 1018
Hey Monero Community !!

Can anyone please guide me on how to create a custom Monero burn address, or generally in the Cryptonote protocol?

Will appreciate your kind help.

Create a wallet in a live environment in ram with a super long password (100+ characters) and don't write down it or the seed. Send your coins to the address. Why do you want to burn your coins?

Yeah, I guess I wasn't specific enough.
I'm looking for a way to create a provably unspendable burn address.
Meaning it should be obvious, for example contain a lot of consecutive X's.

keep generating wallets until you get one with a lot of x's.

this vanity address generator exists

https://monerotalk.org/t/vanity-address-generator/134

https://github.com/ehmry/monero-vanity

so you'll essentially publish the viewkey?


The idea is that nobody will have the private key so nobody will have the possibility to spend the funds.

I want to generate an address, to which it's highly improbable anyone will have the private key.

EDIT: Counterparty created such a BTC address back in the days of their launch

Couldn't you still take the same advice I gave but then take whatever address was given and replace the first 10-15 characters with something along the lines of "xxxxxmoneroxxxxx", then again, the viewkey would no longer work so you wouldn't be able to view it anyway. Interesting.


Will this address be valid? will it be possible to send coins to this address? will it be checksum approved?

Even if it did work, it wouldn't serve the purpose because without a viewkey, you can't prove what the address holds. And since the viewkey is derived from the private key, you won't have a valid viewkey.

I think the best course of action would be to somehow provably create a wallet address without ever retaining the files, seed words, and password. Then you'd still have a view key to see the balance but coins could never be spent. Not sure how you overcome the "trust factor".
hero member
Activity: 532
Merit: 500
Hey Monero Community !!

Can anyone please guide me on how to create a custom Monero burn address, or generally in the Cryptonote protocol?

Will appreciate your kind help.

Create a wallet in a live environment in ram with a super long password (100+ characters) and don't write down it or the seed. Send your coins to the address. Why do you want to burn your coins?

Yeah, I guess I wasn't specific enough.
I'm looking for a way to create a provably unspendable burn address.
Meaning it should be obvious, for example contain a lot of consecutive X's.

keep generating wallets until you get one with a lot of x's.

this vanity address generator exists

https://monerotalk.org/t/vanity-address-generator/134

https://github.com/ehmry/monero-vanity

so you'll essentially publish the viewkey?


The idea is that nobody will have the private key so nobody will have the possibility to spend the funds.

I want to generate an address, to which it's highly improbable anyone will have the private key.

EDIT: Counterparty created such a BTC address back in the days of their launch

Couldn't you still take the same advice I gave but then take whatever address was given and replace the first 10-15 characters with something along the lines of "xxxxxmoneroxxxxx", then again, the viewkey would no longer work so you wouldn't be able to view it anyway. Interesting.


Will this address be valid? will it be possible to send coins to this address? will it be checksum approved?

Theres an easier method:

1) generate 2 wallets.
2) Send coins to one wallet, then send the coins to the second wallet from there and use an unlock_time=9999999999 (seconds - 317 years or so) - for example, or even higher.
3) the transaction cant be spend until the unlock_time is over.
4) You can publish both viewkeys, so everyone can verify it.

legendary
Activity: 1105
Merit: 1000
Hey Monero Community !!

Can anyone please guide me on how to create a custom Monero burn address, or generally in the Cryptonote protocol?

Will appreciate your kind help.

Create a wallet in a live environment in ram with a super long password (100+ characters) and don't write down it or the seed. Send your coins to the address. Why do you want to burn your coins?

Yeah, I guess I wasn't specific enough.
I'm looking for a way to create a provably unspendable burn address.
Meaning it should be obvious, for example contain a lot of consecutive X's.

keep generating wallets until you get one with a lot of x's.

this vanity address generator exists

https://monerotalk.org/t/vanity-address-generator/134

https://github.com/ehmry/monero-vanity

so you'll essentially publish the viewkey?


The idea is that nobody will have the private key so nobody will have the possibility to spend the funds.

I want to generate an address, to which it's highly improbable anyone will have the private key.

EDIT: Counterparty created such a BTC address back in the days of their launch

Couldn't you still take the same advice I gave but then take whatever address was given and replace the first 10-15 characters with something along the lines of "xxxxxmoneroxxxxx", then again, the viewkey would no longer work so you wouldn't be able to view it anyway. Interesting.


Will this address be valid? will it be possible to send coins to this address? will it be checksum approved?

This shouldn't be too difficult to do: You need to generate a real viewkey private/public pair, then "generate" (make up) just a public key for the spend side. You should be able to put these into the address format with its error checking, though I'm not too familiar with the specifics. You *should* then be able to send to this generated account with auditing available, while having them be unspendable.

What would be really neat is an implementation of http://gobittest.appspot.com/ for Cryptonote.

Edit: or I have no idea what I'm talking about.
legendary
Activity: 1442
Merit: 1018
Glad to see you lurking in Monero Oblox  Wink

I've had positions in Monero since last year and at one point, Shadow. It's a niche I believe in.
sr. member
Activity: 341
Merit: 250
Hey Monero Community !!

Can anyone please guide me on how to create a custom Monero burn address, or generally in the Cryptonote protocol?

Will appreciate your kind help.

Create a wallet in a live environment in ram with a super long password (100+ characters) and don't write down it or the seed. Send your coins to the address. Why do you want to burn your coins?

Yeah, I guess I wasn't specific enough.
I'm looking for a way to create a provably unspendable burn address.
Meaning it should be obvious, for example contain a lot of consecutive X's.

keep generating wallets until you get one with a lot of x's.

this vanity address generator exists

https://monerotalk.org/t/vanity-address-generator/134

https://github.com/ehmry/monero-vanity

so you'll essentially publish the viewkey?


The idea is that nobody will have the private key so nobody will have the possibility to spend the funds.

I want to generate an address, to which it's highly improbable anyone will have the private key.

EDIT: Counterparty created such a BTC address back in the days of their launch

Couldn't you still take the same advice I gave but then take whatever address was given and replace the first 10-15 characters with something along the lines of "xxxxxmoneroxxxxx", then again, the viewkey would no longer work so you wouldn't be able to view it anyway. Interesting.


Will this address be valid? will it be possible to send coins to this address? will it be checksum approved?
sr. member
Activity: 462
Merit: 500
Glad to see you lurking in Monero Oblox  Wink
newbie
Activity: 55
Merit: 0
Interesting. Its looks like using the daemon to CPU mine does not affect RAM usage at all - I've got 3 threads hashing away there.
donator
Activity: 1274
Merit: 1060
GetMonero.org / MyMonero.com
No dice on tewinget's branch. I do see a lmdb out of space error in addition to the uncaught exception but there is well over 11gb of free space, not factoring in the 3.4gb blockchain.bin that monero already takes up.

Ok I'm going to need more info -

1. What Windows version, and 32-bit or 64-bit?

2. What is the LMDB error, is it something like "MDB_MAP_FULL Environment mapsize limit reached" ?
legendary
Activity: 1442
Merit: 1018
user@user-PC MINGW64 ~/bitmonero-master/src/build

Maybe you are on the wrong starting directory. Should that be bitmonero-master/build?



Good call. I guess I assumed the source directory was the actual src directory and not the root of the github pull. This allowed me to build but when I run the bitmonerod.exe file built, it crashes with the log pointing to:

2015-Apr-09 06:01:49.582503 ERROR C:/msys64/home/user/bitmonero-master/src/daemon/daemon.cpp:145 Uncaught exception! Failed to initialize core
2015-Apr-09 06:01:49.582503 Deinitializing rpc server...
2015-Apr-09 06:01:49.582503 Deinitializing p2p..

I don't recommend compiling from git head if you want it to be stable, we've *just* done a bunch of merges and there are known issues as well as other unexpected hiccups. You can checkout the 0.8.8.6 git tag if you want a more stable build.

I'm mainly after trying the new db in a windows environment since the existing daemon uses about 6.2gb of memory and from the linux screenshots I've been seeing, this has been reduced to around 34mb iirc. To my knowledge, that tag would not include the latest db merge which is the sole purpose of this build.

You might try the blockchain branch (=db), since people have been using that for a while, and that avoids all the merge issues. Not sure about Windows builds from that though.

I second that - rather build the blockchainDB branch (pre-merge) - https://github.com/tewinget/bitmonero/tree/blockchain

Edit: forgot to add, most of my testing has been OS X, ARM, and Windows. A large portion of development was done in a Linux environment, but we test on everything:)

I'm in the process of building that one and we'll see what happens. Doesn't take terribly long on an 8-core w/ 16g ram.

No dice on tewinget's branch. I do see a lmdb out of space error in addition to the uncaught exception but there is well over 11gb of free space, not factoring in the 3.4gb blockchain.bin that monero already takes up.
newbie
Activity: 55
Merit: 0
I'm mainly after trying the new db in a windows environment since the existing daemon uses about 6.2gb of memory and from the linux screenshots I've been seeing, this has been reduced to around 34mb iirc. To my knowledge, that tag would not include the latest db merge which is the sole purpose of this build. I'd love to be able to try it, especially since it seems most testing has been on linux environments.

It is actually less than 30MB on my Ubuntu box. Also, I noticed the daemon starts and stops a lot faster than before!  Great work devs Cheesy
legendary
Activity: 1442
Merit: 1018
user@user-PC MINGW64 ~/bitmonero-master/src/build

Maybe you are on the wrong starting directory. Should that be bitmonero-master/build?



Good call. I guess I assumed the source directory was the actual src directory and not the root of the github pull. This allowed me to build but when I run the bitmonerod.exe file built, it crashes with the log pointing to:

2015-Apr-09 06:01:49.582503 ERROR C:/msys64/home/user/bitmonero-master/src/daemon/daemon.cpp:145 Uncaught exception! Failed to initialize core
2015-Apr-09 06:01:49.582503 Deinitializing rpc server...
2015-Apr-09 06:01:49.582503 Deinitializing p2p..

I don't recommend compiling from git head if you want it to be stable, we've *just* done a bunch of merges and there are known issues as well as other unexpected hiccups. You can checkout the 0.8.8.6 git tag if you want a more stable build.

I'm mainly after trying the new db in a windows environment since the existing daemon uses about 6.2gb of memory and from the linux screenshots I've been seeing, this has been reduced to around 34mb iirc. To my knowledge, that tag would not include the latest db merge which is the sole purpose of this build.

You might try the blockchain branch (=db), since people have been using that for a while, and that avoids all the merge issues. Not sure about Windows builds from that though.

I second that - rather build the blockchainDB branch (pre-merge) - https://github.com/tewinget/bitmonero/tree/blockchain

Edit: forgot to add, most of my testing has been OS X, ARM, and Windows. A large portion of development was done in a Linux environment, but we test on everything:)

I'm in the process of building that one and we'll see what happens. Doesn't take terribly long on an 8-core w/ 16g ram.
donator
Activity: 1274
Merit: 1060
GetMonero.org / MyMonero.com
user@user-PC MINGW64 ~/bitmonero-master/src/build

Maybe you are on the wrong starting directory. Should that be bitmonero-master/build?



Good call. I guess I assumed the source directory was the actual src directory and not the root of the github pull. This allowed me to build but when I run the bitmonerod.exe file built, it crashes with the log pointing to:

2015-Apr-09 06:01:49.582503 ERROR C:/msys64/home/user/bitmonero-master/src/daemon/daemon.cpp:145 Uncaught exception! Failed to initialize core
2015-Apr-09 06:01:49.582503 Deinitializing rpc server...
2015-Apr-09 06:01:49.582503 Deinitializing p2p..

I don't recommend compiling from git head if you want it to be stable, we've *just* done a bunch of merges and there are known issues as well as other unexpected hiccups. You can checkout the 0.8.8.6 git tag if you want a more stable build.

I'm mainly after trying the new db in a windows environment since the existing daemon uses about 6.2gb of memory and from the linux screenshots I've been seeing, this has been reduced to around 34mb iirc. To my knowledge, that tag would not include the latest db merge which is the sole purpose of this build.

You might try the blockchain branch (=db), since people have been using that for a while, and that avoids all the merge issues. Not sure about Windows builds from that though.

I second that - rather build the blockchainDB branch (pre-merge) - https://github.com/tewinget/bitmonero/tree/blockchain

Edit: forgot to add, most of my testing has been OS X, ARM, and Windows. A large portion of development was done in a Linux environment, but we test on everything:)
legendary
Activity: 2968
Merit: 1198
user@user-PC MINGW64 ~/bitmonero-master/src/build

Maybe you are on the wrong starting directory. Should that be bitmonero-master/build?



Good call. I guess I assumed the source directory was the actual src directory and not the root of the github pull. This allowed me to build but when I run the bitmonerod.exe file built, it crashes with the log pointing to:

2015-Apr-09 06:01:49.582503 ERROR C:/msys64/home/user/bitmonero-master/src/daemon/daemon.cpp:145 Uncaught exception! Failed to initialize core
2015-Apr-09 06:01:49.582503 Deinitializing rpc server...
2015-Apr-09 06:01:49.582503 Deinitializing p2p..

I don't recommend compiling from git head if you want it to be stable, we've *just* done a bunch of merges and there are known issues as well as other unexpected hiccups. You can checkout the 0.8.8.6 git tag if you want a more stable build.

I'm mainly after trying the new db in a windows environment since the existing daemon uses about 6.2gb of memory and from the linux screenshots I've been seeing, this has been reduced to around 34mb iirc. To my knowledge, that tag would not include the latest db merge which is the sole purpose of this build.

You might try the blockchain branch (=db), since people have been using that for a while, and that avoids all the merge issues. Not sure about Windows builds from that though.
legendary
Activity: 1442
Merit: 1018
user@user-PC MINGW64 ~/bitmonero-master/src/build

Maybe you are on the wrong starting directory. Should that be bitmonero-master/build?



Good call. I guess I assumed the source directory was the actual src directory and not the root of the github pull. This allowed me to build but when I run the bitmonerod.exe file built, it crashes with the log pointing to:

2015-Apr-09 06:01:49.582503 ERROR C:/msys64/home/user/bitmonero-master/src/daemon/daemon.cpp:145 Uncaught exception! Failed to initialize core
2015-Apr-09 06:01:49.582503 Deinitializing rpc server...
2015-Apr-09 06:01:49.582503 Deinitializing p2p..

I don't recommend compiling from git head if you want it to be stable, we've *just* done a bunch of merges and there are known issues as well as other unexpected hiccups. You can checkout the 0.8.8.6 git tag if you want a more stable build.

I'm mainly after trying the new db in a windows environment since the existing daemon uses about 6.2gb of memory and from the linux screenshots I've been seeing, this has been reduced to around 34mb iirc. To my knowledge, that tag would not include the latest db merge which is the sole purpose of this build. I'd love to be able to try it, especially since it seems most testing has been on linux environments.
Jump to: