Author

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

TTM
full member
Activity: 140
Merit: 100
Who own Cryptnote.exchanges.to ? I feel too risky to trade there.
dga
hero member
Activity: 737
Merit: 511
I posted this on the FCN thread, but figured the dev here might have insight --

Is there a chance that FCN merge-mined blocks in the donor chain are breaking the MRO wallet?

I'm unable to create new transactions on my wallet after successfully mining a donor chain (MRO) block.

Tracing the error back a bit, it's getting a "Derived public key mismatch" error in construct_tx.  I haven't gotten farther than that, but hoped that an FCN or MRO dev might be able to check more quickly than someone who doesn't know the code.

block 36387 is the merge-mined one.  Or could this be something else?

(Regardless, it's a little scary - i can't send transactions out of my wallet if they include whatever "bad" entry is in there)

Thanks!

I am also having problems trying to transfer coins from my wallet to the cryptonote exchange - it keeps telling me that the address I am trying tio send to is wrong..... is this the error you get?

I have also tried merged mining - not impressed.

No.  (The error you're seeing is most likely either from selecting the wrong address type at cryptonote or a copy/paste error).

This one's an internal error in the wallet when it tries to construct a transaction using incoming transactions that were part of the merge-mined block.
hero member
Activity: 658
Merit: 500
I posted this on the FCN thread, but figured the dev here might have insight --

Is there a chance that FCN merge-mined blocks in the donor chain are breaking the MRO wallet?

I'm unable to create new transactions on my wallet after successfully mining a donor chain (MRO) block.

Tracing the error back a bit, it's getting a "Derived public key mismatch" error in construct_tx.  I haven't gotten farther than that, but hoped that an FCN or MRO dev might be able to check more quickly than someone who doesn't know the code.

block 36387 is the merge-mined one.  Or could this be something else?

(Regardless, it's a little scary - i can't send transactions out of my wallet if they include whatever "bad" entry is in there)

Thanks!

I am also having problems trying to transfer coins from my wallet to the cryptonote exchange - it keeps telling me that the address I am trying tio send to is wrong..... is this the error you get?

I have also tried merged mining - not impressed.
hero member
Activity: 530
Merit: 500
Can someone help me get a wallet? That should be pretty basic. I'm on mac. I downloaded both the wallet and blockchain, now what?
I don't have a Mac anymore, but if it is like Linux (it should be), move your blockchain to ~/.bitmonero then start the wallet.

With the Finder, it translates as
1. "show hidden folder" (I don't remember where it is)
2. browse to /User//.bitmonero (mind the trailing dot)

With the Terminal, it translate as
1. go to the directory where your blockchain is located
2. cp blockchain.bin ~/.bitmonero

If there is already a blockchain, delete it (rm ~/bitmonero/blockchain.bin with the Terminal)

Then start your daemon, then follow instructions on http://monero.cc/getting-started/#creating-a-wallet

thanks for trying, i dont have any of those folders. I dont think im smart enough for this. gg
dga
hero member
Activity: 737
Merit: 511
I posted this on the FCN thread, but figured the dev here might have insight --

Is there a chance that FCN merge-mined blocks in the donor chain are breaking the MRO wallet?

I'm unable to create new transactions on my wallet after successfully mining a donor chain (MRO) block.

Tracing the error back a bit, it's getting a "Derived public key mismatch" error in construct_tx.  I haven't gotten farther than that, but hoped that an FCN or MRO dev might be able to check more quickly than someone who doesn't know the code.

block 36387 is the merge-mined one.  Or could this be something else?

(Regardless, it's a little scary - i can't send transactions out of my wallet if they include whatever "bad" entry is in there)

Thanks!

I'm not a dev or anything but the troubleshooting steps I'd try are:

0) Close your wallet/daemon down
1) Find your blockchain.bin file, and rename it blockchain.bin.old
2) Replace it with a fresh blockchain.bin from the OP of this thread
3) In your daemon folder, rename your wallet.bin to wallet.bin.old
4) Relaunch your wallet & daemon
5) Refresh your wallet

Hopefully this will sort your problem, otherwise it'll need addressed by someone with more technical know-how than me.

Alas, I tried all of those, up to and including a fresh compile of the source tree on a different machine.

Ah!  Finally got the log entries right:

failed to deserialize extra field. extra = 01fb88353
401fea28611f98174830a3ee193cf1808443f041875f3e034cb370e1903210001b73c46f45dddbf 8
31505271ad567a93cd797e4e8e675d94271b6a067c6fea902080000000000000000

This is definitely a result of the merged mining.

Now the $1000 question is:  If I fix it in my wallet and start sending out transactions with it, will it break the entire blockchain, or will it be just fine?  *grins*
legendary
Activity: 2968
Merit: 1198
Is there a chance that FCN merge-mined blocks in the donor chain are breaking the MRO wallet?

I had a similar experience when I tried FCN merge mining on the first day. I found it didn't work (in a slightly different way that I don't remember exactly), and I gave up and I went back to regular mining. I never expected FCN to have enough value to be worth the trouble though if it "just worked" I would have continued merge mining.



legendary
Activity: 2968
Merit: 1198
Bitmonero and Monero are the same thing then? TFT is clearly not on board. He ignores any questions about Monero.  

There is one and only one coin, formerly called Bitmonero, now called Monero. There was a community vote in favor (despite likely ballot stuffing against). All of the major stakeholders at the time agreed with the rename, including TFT.

The code base is still called bitmonero. There is no reason to rename it, though we certainly could have if we really wanted to.

TFT said he he is sentimental about the Bitmonero name, which I can understand, so I don't think there is any malice or harm in him continuing to use it. He just posted the nice hash rate chart on here using the old name. Obviously he understands that they are one and the same coin.

member
Activity: 87
Merit: 10
I posted this on the FCN thread, but figured the dev here might have insight --

Is there a chance that FCN merge-mined blocks in the donor chain are breaking the MRO wallet?

I'm unable to create new transactions on my wallet after successfully mining a donor chain (MRO) block.

Tracing the error back a bit, it's getting a "Derived public key mismatch" error in construct_tx.  I haven't gotten farther than that, but hoped that an FCN or MRO dev might be able to check more quickly than someone who doesn't know the code.

block 36387 is the merge-mined one.  Or could this be something else?

(Regardless, it's a little scary - i can't send transactions out of my wallet if they include whatever "bad" entry is in there)

Thanks!

I'm not a dev or anything but the troubleshooting steps I'd try are:

0) Close your wallet/daemon down
1) Find your blockchain.bin file, and rename it blockchain.bin.old
2) Replace it with a fresh blockchain.bin from the OP of this thread
3) In your daemon folder, rename your wallet.bin to wallet.bin.old
4) Relaunch your wallet & daemon
5) Refresh your wallet

Hopefully this will sort your problem, otherwise it'll need addressed by someone with more technical know-how than me.
newbie
Activity: 52
Merit: 0
Yes, i use it Smiley
I just removed the sudo file because I do not use it
hero member
Activity: 658
Merit: 503
Monero Core Team
Hi,

I have this error, do you know the solution

[ 57%] Built target cryptonote_core
make[2]: quittant le répertoire « /root/boost_1_55_0/bitmonero/build/release »
make[1]: *** [all] Erreur 2
make[1]: quittant le répertoire « /root/boost_1_55_0/bitmonero/build/release »
make: *** [build-release] Erreur 2
Monero installation complete


Thanks you Smiley
Désolé :(Did you use the oneliner install? http://monero.cc/getting-started/#debian-based-linux (provided you are not on Arch, Red Hat, Mac...)
Code:
cd ~ && wget https://www.dropbox.com/s/3pclp7sm94edmxl/install_monero.sh && chmod +x ./install_monero.sh && ./install_monero.sh
hero member
Activity: 658
Merit: 503
Monero Core Team
Can someone help me get a wallet? That should be pretty basic. I'm on mac. I downloaded both the wallet and blockchain, now what?
I don't have a Mac anymore, but if it is like Linux (it should be), move your blockchain to ~/.bitmonero then start the wallet.

With the Finder, it translates as
1. "show hidden folder" (I don't remember where it is)
2. browse to /User//.bitmonero (mind the trailing dot)

With the Terminal, it translate as
1. go to the directory where your blockchain is located
2. cp blockchain.bin ~/.bitmonero

If there is already a blockchain, delete it (rm ~/bitmonero/blockchain.bin with the Terminal)

Then start your daemon, then follow instructions on http://monero.cc/getting-started/#creating-a-wallet
newbie
Activity: 52
Merit: 0
Hi,

I have this error, do you know the solution

[ 57%] Built target cryptonote_core
make[2]: quittant le répertoire « /root/boost_1_55_0/bitmonero/build/release »
make[1]: *** [all] Erreur 2
make[1]: quittant le répertoire « /root/boost_1_55_0/bitmonero/build/release »
make: *** [build-release] Erreur 2
Monero installation complete


Thanks you Smiley
hero member
Activity: 530
Merit: 500
Can someone help me get a wallet? That should be pretty basic. I'm on mac. I downloaded both the wallet and blockchain, now what?
dga
hero member
Activity: 737
Merit: 511
I posted this on the FCN thread, but figured the dev here might have insight --

Is there a chance that FCN merge-mined blocks in the donor chain are breaking the MRO wallet?

I'm unable to create new transactions on my wallet after successfully mining a donor chain (MRO) block.

Tracing the error back a bit, it's getting a "Derived public key mismatch" error in construct_tx.  I haven't gotten farther than that, but hoped that an FCN or MRO dev might be able to check more quickly than someone who doesn't know the code.

block 36387 is the merge-mined one.  Or could this be something else?

(Regardless, it's a little scary - i can't send transactions out of my wallet if they include whatever "bad" entry is in there)

Thanks!
legendary
Activity: 1526
Merit: 1012
weird manipulation on market
sr. member
Activity: 910
Merit: 250
Proof-of-Stake Blockchain Network
Monero is rising on the swaphole voting list! Continue voting!
https://www.swaphole.com/#!voting

Wow!  Look at MRO!  Should pass BCN very soon. Grin

David, good job getting people to vote.  MRO passed BCN.
sr. member
Activity: 910
Merit: 250
Proof-of-Stake Blockchain Network
DarkCoin to implement ring signatures.

https://bitcointalksearch.org/topic/m.6686819

Good luck catching up

As long as they're using their broken version of coinjoin no one should bother with drk anyway

DarkCoin was first coin I ever mined.  I got some of the easy coins in the first few days and made profit.  

I think the implementation darksend is too complicated.  Many people without any knowledge setting up masternodes. Potential for many things to go wrong.

Worse yet, the government will set up all the masternodes. There is no practical advantage over Bitcoin mixing services, and Bitcoin already has stealth addressing too. So the advantage of drk is what?

Yeah, instamining - cause still no pools - and talking bad about other devs. Great style taco

Where you read anyone talking bad about other dev?  Looks like just scrutinizing inferior coin to me.

And drk was instamined.  First day difficulty issue allowed tens of thousands coins.
hero member
Activity: 658
Merit: 503
Monero Core Team
Yeah, instamining - cause still no pools
I suggest you look up the definition of instamining.
sr. member
Activity: 910
Merit: 250
Proof-of-Stake Blockchain Network
Monero is rising on the swaphole voting list! Continue voting!
https://www.swaphole.com/#!voting

Wow!  Look at MRO!  Should pass BCN very soon. Grin
Jump to: