Come on, proof-of-haiku, really? The "core team" failed for several weeks and potentially exposed every XMR user with a bug leading to money loss. Could you make a haiku on that?
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1604. (Read 4670972 times)
It's wonderful to see how Monero PR team works. Everytime there's a painful topic in this thread, some new members arrive and start posting irrelevant bullshit. You're doing great guys!
Come on, proof-of-haiku, really? The "core team" failed for several weeks and potentially exposed every XMR user with a bug leading to money loss. Could you make a haiku on that?
Come on, proof-of-haiku, really? The "core team" failed for several weeks and potentially exposed every XMR user with a bug leading to money loss. Could you make a haiku on that?
After many hours of study I have found the only computational cipher worthy of my study and mastery is: PoH.
Obviously you are too dimwitted to have even considered using PoH to secure the Monero blockchain. But allow me to elucidate you slightly.
...
Yes, the Proof of Haiku algorithm is even capable of withstanding the coming rigors of quantum computing, and cannot be broken by the NSA until, by my calculations, sometime in the fall of 2065. I would like to pinpoint the date more accurately, but as the original cryptopoet Bashō wrote:
Obviously you are too dimwitted to have even considered using PoH to secure the Monero blockchain. But allow me to elucidate you slightly.
...
Yes, the Proof of Haiku algorithm is even capable of withstanding the coming rigors of quantum computing, and cannot be broken by the NSA until, by my calculations, sometime in the fall of 2065. I would like to pinpoint the date more accurately, but as the original cryptopoet Bashō wrote:
100 XMR bounty for open-source Proof-of-Haiku!
I think there's also a 50 XMR bounty for an open-source Cryptonight abacus, still waiting to be claimed also!
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
A few little queries about transaction fees. Let's say I have two hypothetical wallets.
Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
Why don't you just copy wallet.dat or import private keys than transferring it?
Kindly,
MZ
I am personally doing a small survey about XMR for all the people interested in completing it :
https://docs.google.com/forms/d/1JqIXkjKpcEpv6lyH6SD22f_Ny0i-rhM9bV21WcOFstw/viewform
https://docs.google.com/forms/d/1JqIXkjKpcEpv6lyH6SD22f_Ny0i-rhM9bV21WcOFstw/viewform
Awesome survey, can't wait to see some of the results!
Not sure I understand 3. I was the miner for some transactions (through a pool), and the purchaser on polo for the bigger transactions. I thought the transaction fees were going to the devs.
The tx fees do not go to the devs.
orly?
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
This is true. Today we at MinerGate updated our XMR daemons and wallets to the latest github version, but fortunately the wallet didn't pass our sanity check tests, because of PaymentID being skipped for every tx.
I've created a pull request with a fix, please take a look.
https://github.com/monero-project/bitmonero/pull/69
UPD: fluffypony accepts my request, thanks!
Thank you Minergate for helping out incompetent XMR developers. They should be very grateful this was fixed so fast, could've been much worse.
Imagine what would happen if this went unnoticed - a lot of people with a lot of lost funds all due to a childish mistake.
I love how all monero shills now sit tight and don't post shit. Quite... can hear birds singing. I like that.
dnote has had quite a few replies and I very happy with tacotime's response, very professional.
On the other hand, you're being very childish.
Not sure I understand 3. I was the miner for some transactions (through a pool), and the purchaser on polo for the bigger transactions. I thought the transaction fees were going to the devs.
Transaction fees are going to the miners - when you are mining for a pool it's distributed to all the pool miners depending on their hash power (when the pool fee is subtracted). 
I love how all monero shills now sit tight and don't post shit. Quite... can hear birds singing. I like that.
orly?
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
This is true. Today we at MinerGate updated our XMR daemons and wallets to the latest github version, but fortunately the wallet didn't pass our sanity check tests, because of PaymentID being skipped for every tx.
I've created a pull request with a fix, please take a look.
https://github.com/monero-project/bitmonero/pull/69
UPD: fluffypony accepted my request, thanks!
I am personally doing a small survey about XMR for all the people interested in completing it :
https://docs.google.com/forms/d/1JqIXkjKpcEpv6lyH6SD22f_Ny0i-rhM9bV21WcOFstw/viewform
Thanks in advance
https://docs.google.com/forms/d/1JqIXkjKpcEpv6lyH6SD22f_Ny0i-rhM9bV21WcOFstw/viewform
Thanks in advance
Did it
Nice result page
A few little queries about transaction fees. Let's say I have two hypothetical wallets.
Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
1) Probably most of it, but not all of it - you should try.Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
2) Each transaction will have 0.005 fee
3) To the miners
4) Most probably if the price goes up by significant factor the fee will go down (for the same maximum size of the transaction).
Not sure I understand 3. I was the miner for some transactions (through a pool), and the purchaser on polo for the bigger transactions. I thought the transaction fees were going to the devs.
orly?
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
Is this in 0.8.8 or in master ?
I'll quote dNote on this:
-snip-
Well, I'll cut-and-paste my reply to you from Github:
Quote
@ducknote Please don't act stupid, you're better than this.
1. You're conflating - that was pulled into the code long before there were any Monero developers: https://github.com/monero-project/bitmonero/commit/333f975760c156727dd7408f87e937af856d8bf1. We have not failed to credit the CryptoNote developers, and where there is code that is merged from other CryptoNote projects we ALWAYS credit the source. For example, we have credited Boolberry on more than one occasion: https://github.com/monero-project/bitmonero/commit/c050ff43bf5a8310b18081c5cd3d9bcd123416b8, https://github.com/monero-project/bitmonero/commit/3bc16dc0e6bd38fbec51a054e640bacdb17a9a82. Similarly, Boolberry have credited us on more than one occasion: https://github.com/cryptozoidberg/boolberry/commit/f7a019683a2ecc1954b761ac7094d588644ecf1c, https://github.com/cryptozoidberg/boolberry/commit/88bfcbf6d067a3f15f3d22a87dcb54211dc11f17, and https://github.com/cryptozoidberg/boolberry/commit/0ae9a2f24757e7229cf63776b5897c5b408c065e.
2. I've never heard of a "golden ampersand" bug, and neither has Google. Either you're outrightly lying, or you're using the wrong term entirely. Regardless, your ad hominem attack is nothing more than a straw man argument to try and detract from your despicable failure to credit the authors of the code you have merged down.
To be specific, again, this functionality (the payment ID being available in the JSON RPC transfer call) is not something you wrote. It is something we wrote. I have already linked you to the commit where it was merged on June 2nd. Don't worry - you're not the only one that has failed to credit Monero, Bytecoin also added the change on June 25th, stripped the code comments, and failed to credit us.
If you wish to remain honourable it would be appropriate for you not to insult me or any of the contributors to Monero, and to credit us where you have used our code. Of course, if there is anything you write that we use we will most definitely credit you, just as we have done with Boolberry.
1. You're conflating - that was pulled into the code long before there were any Monero developers: https://github.com/monero-project/bitmonero/commit/333f975760c156727dd7408f87e937af856d8bf1. We have not failed to credit the CryptoNote developers, and where there is code that is merged from other CryptoNote projects we ALWAYS credit the source. For example, we have credited Boolberry on more than one occasion: https://github.com/monero-project/bitmonero/commit/c050ff43bf5a8310b18081c5cd3d9bcd123416b8, https://github.com/monero-project/bitmonero/commit/3bc16dc0e6bd38fbec51a054e640bacdb17a9a82. Similarly, Boolberry have credited us on more than one occasion: https://github.com/cryptozoidberg/boolberry/commit/f7a019683a2ecc1954b761ac7094d588644ecf1c, https://github.com/cryptozoidberg/boolberry/commit/88bfcbf6d067a3f15f3d22a87dcb54211dc11f17, and https://github.com/cryptozoidberg/boolberry/commit/0ae9a2f24757e7229cf63776b5897c5b408c065e.
2. I've never heard of a "golden ampersand" bug, and neither has Google. Either you're outrightly lying, or you're using the wrong term entirely. Regardless, your ad hominem attack is nothing more than a straw man argument to try and detract from your despicable failure to credit the authors of the code you have merged down.
To be specific, again, this functionality (the payment ID being available in the JSON RPC transfer call) is not something you wrote. It is something we wrote. I have already linked you to the commit where it was merged on June 2nd. Don't worry - you're not the only one that has failed to credit Monero, Bytecoin also added the change on June 25th, stripped the code comments, and failed to credit us.
If you wish to remain honourable it would be appropriate for you not to insult me or any of the contributors to Monero, and to credit us where you have used our code. Of course, if there is anything you write that we use we will most definitely credit you, just as we have done with Boolberry.
Code gets committed to staging so it can be tested. The piece of code you're referring to is not in the 0.8.8 tagged release, and is thus not finalised. Thanks for pointing out the error, but nobody has lost anything.
lolollol "golden ampersand" bug - is mine © - i call it golden because just one "&" can cause a lot of money loss by monero users.
Again - Transaction ID was implemented in Bytecoin long before monero made it - https://github.com/amjuarez/bytecoin/commit/57cf53625817223733bdaf2f4e518ebae978713e April 29.
Monero just made it in RPC call, that part of kiddy code was ok, but nothing special and nothing hard. and at least that part of monero code was ok.
AGAIN:
Quote
Code gets committed to staging so it can be tested. The piece of code you're referring to is not in the 0.8.8 tagged release, and is thus not finalised. Thanks for pointing out the error, but nobody has lost anything.
Lets do like that:
1. Go to http://monero.cc
2. Click Getting Started link
http://monero.cc/getting-started/index.html3. Click http://monero.cc/getting-started/index.html#install_source
4. Here we can read: git clone git://github.com/monero-project/bitmonero && cd bitmonero && make
5. Go to the suggested code, master branch -> commits: https://github.com/monero-project/bitmonero/commits/master
6. Find that commit https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2 on master branch
7. Profit! Monero got "golden ampersand" bug since that commit, means since June 18th. All exchanges and services that made source code compilation from monero master branch since June 18th affected.
A few little queries about transaction fees. Let's say I have two hypothetical wallets.
Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
1) Probably most of it, but not all of it - you should try.Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
2) Each transaction will have 0.005 fee
3) To the miners
4) Most probably if the price goes up by significant factor the fee will go down (for the same maximum size of the transaction).
So, basically you wasted users money because of your incompetence?
Wasn't my code or my merge; when devs commit things to HEAD we warn everyone that they're experimental.
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
This was somehow merged despite it being fixed a while ago while in testing
https://github.com/tewinget/bitmonero/commit/e7a3bd19f61d047f3daa49910e0d7da41ef47a8b
It was neglected to be merged in with the latest bunch of commits due to an oversight
So, basically you wasted users money because of your incompetence?
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
This was somehow merged despite it being fixed a while ago while in testing
https://github.com/tewinget/bitmonero/commit/e7a3bd19f61d047f3daa49910e0d7da41ef47a8b
It was neglected to be merged in with the latest bunch of commits due to an oversight
A few little queries about transaction fees. Let's say I have two hypothetical wallets.
Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
Old, dusty wallet 1 has 100 dust (<0.1) transactions from mining, 50 small transactions of .2, and 10 larger (>100) transactions from exchange transfers. No transactions out.
New, shiny wallet 2 is empty.
Now, if I were to transfer everything from wallet 1 to wallet 2 in a single transaction:
1) Would this go through as a single transaction?
2) What transaction fee would be payable?
3) Where do transaction fees go?
4) How will transaction fees be changing in the future?
Loving the Monero by the way. Don't let the FUD'ers bother you.
Cheers, Q
monero devs seems to be absolutely beginners - your accusations and anger touched us, here is a result of 10 min research of your kiddy coding, concerning Payments ID and games with your kiddy coin wallet:
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.
Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2
With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:
bool validate_transfer(const std::list destinations, const std::string payment_id, std::vector& dsts, std::vector& extra, epee::json_rpc::error& er);
bool wallet_rpc_server::validate_transfer(const std::list destinations, const std::string payment_id, std::vector& dsts, std::vector& extra, epee::json_rpc::error& er)
Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...
Users, be careful with kiddy coders.
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.
Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2
With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:
bool validate_transfer(const std::list
bool wallet_rpc_server::validate_transfer(const std::list
Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...
Users, be careful with kiddy coders.
Well this is awkward.
Allmighty monero devs are not so allmighty after all. And there was so much marketing about it... it's not even fun, it's just sad.
So, that's why my XMR from hitbtc didn't reach Poloniex. And I was asking myself what I did wrong.
No its not, this piece of code is not in the latest tagged realease. See here for fluffyponys response.
https://bitcointalksearch.org/topic/m.7987794
orly?
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.h#L52
https://github.com/monero-project/bitmonero/blob/master/src/wallet/wallet_rpc_server.cpp#L142
monero devs seems to be absolutely beginners - your accusations and anger touched us, here is a result of 10 min research of your kiddy coding, concerning Payments ID and games with your kiddy coin wallet:
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.
Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2
With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:
bool validate_transfer(const std::list destinations, const std::string payment_id, std::vector& dsts, std::vector& extra, epee::json_rpc::error& er);
bool wallet_rpc_server::validate_transfer(const std::list destinations, const std::string payment_id, std::vector& dsts, std::vector& extra, epee::json_rpc::error& er)
Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...
Users, be careful with kiddy coders.
Second chapter of any average "Beginners in C++ guide" says that arguments can be passed to parameters either by value or by reference.
Looks like monero devs did not noticed that, when they recently read that kind of books.
Lets look at this playground:
https://github.com/monero-project/bitmonero/commit/d433a696e527a01c1cbef48495652335140f0bb2
With "Monero golden ampersand bug" made by monero devs, monero devs missed some &, wuuups:
bool validate_transfer(const std::list
bool wallet_rpc_server::validate_transfer(const std::list
Affects: Monero simplewallet since at least June 18 just lose all Payment ID data, so people can lost their money if they use your so called monero RPC "features". Again - all transfers in monero network made with JSON-RPC Payment ID, EG from Poloniex exchange to Bittrex exchange was made wrong if they use monero latest main kiddy code, or may be just lost. Qua, qua, qua ...
Users, be careful with kiddy coders.
Well this is awkward.
Allmighty monero devs are not so allmighty after all. And there was so much marketing about it... it's not even fun, it's just sad.
So, that's why my XMR from hitbtc didn't reach Poloniex. And I was asking myself what I did wrong.
No its not, this piece of code is not in the latest tagged realease. See here for fluffyponys response.
https://bitcointalksearch.org/topic/m.7987794
Jump to: