Author

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

sr. member
Activity: 373
Merit: 250
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.



Well this is awkward. Grin Allmighty monero devs are not so allmighty after all.  Grin

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.

Re-reading Poloniex announcements:



Thanks to the XMR devs the payments are order of magnitude faster at losing user's money. So lol.
sr. member
Activity: 525
Merit: 250
Dear HitBTC Users,

Regarding your numerous questions on the possible reasons of XMR payments not being processed correctly, we would like to inform you that the bug which caused the above-mentioned issue has been identified: due to a common technical issue, the transaction IDs were not sent to the XMR blockchain since 22/07/2014 11:30 UTC.

While this bug has not affected users who were withdrawing Monero to their own wallets, it affected the users who were transferring Monero directly between their accounts at different cryptocurrency exchanges, including HitBTC. The consequence being that the coins transferred directly from one exchange to another did not contain a payment ID, preventing users’ trading account from being credited.

At the present moment the problem has already been solved. We also inform you that HitBTC has cooperated with the involved exchanges on crediting users their funds.

In case you encounter any difficulties withdrawing or depositing Monero, please contact our Support team, and we will investigate the case in shortest time possible.

Regards,
the HitBTC team
sr. member
Activity: 692
Merit: 254
terra-credit.com
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.



Well this is awkward. Grin Allmighty monero devs are not so allmighty after all.  Grin

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.
xa4
member
Activity: 71
Merit: 10
Can I just say that Ethereum isn't really our enemy.

Ethereum cannot offer anonymity, and if they implement something like ring signatures, they will be far less efficient than a native currency such as Monero.

Ethereum is going against a bit of Bitcoin but mostly it's generating it's own market.

Correct me if you think I am wrong, I'm really interested in hearing other peoples thoughts on the matter.

Acccording to V.Buterin you could implement a ring signatures algo in a contract and have 1 on 1 peg with the underlying ethers (ETH) -> your selfmade currency and underlying ethers would be annonymous.

http://redd.it/2b7gpd

Ethereum is very promising, but we'll have to see if the technology actually works. If it lives up to it's promise, I think it will become THE platform for smart contracts, ... and now is the time to look for options, ideas on how to make them work together.(EDIT Monero and ethereum)
sr. member
Activity: 728
Merit: 265
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.



Well this is awkward. Grin Allmighty monero devs are not so allmighty after all.  Grin

And there was so much marketing about it... it's not even fun, it's just sad.
hero member
Activity: 532
Merit: 500
Currently held as collateral by monbux
Can I just say that Ethereum isn't really our enemy.

Ethereum cannot offer anonymity, and if they implement something like ring signatures, they will be far less efficient than a native currency such as Monero.

Ethereum is going against a bit of Bitcoin but mostly it's generating it's own market.

Correct me if you think I am wrong, I'm really interested in hearing other peoples thoughts on the matter.

I don't think there's any threat on monero from any alt coin this is a great coin which has been proven to work and has already been established.
legendary
Activity: 2296
Merit: 1031
What's the formula to calculate time in hours to find a block?  like in btc/ltc this seems to work:

Code:
time to block in hours = ((2^32*difficulty) / hashrate)) / 60 / 60

But that doesn't work for XMR. 
legendary
Activity: 1176
Merit: 1015
Can I just say that Ethereum isn't really our enemy.

Ethereum cannot offer anonymity, and if they implement something like ring signatures, they will be far less efficient than a native currency such as Monero.

Ethereum is going against a bit of Bitcoin but mostly it's generating it's own market.

Correct me if you think I am wrong, I'm really interested in hearing other peoples thoughts on the matter.
legendary
Activity: 1106
Merit: 1000
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


Did it
member
Activity: 73
Merit: 10
Searching a place to mine XMR?  Grin

Help us to brake some blocks & spread the hashes !  Cheesy


XMR MINING POOL >> http://xmr.poolto.be

use : stratum+tcp://xmr.poolto.be:3001

Happy Mining !  Smiley

pool fee: 0.20% (pool) + 0.1% (node-crypto dev/xmr core dev) to support XMR ! >> JOIN US!
r05
full member
Activity: 193
Merit: 100
test cryptocoin please ignore
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

Just done that for you now.
hero member
Activity: 565
Merit: 500
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

What is the survey for and what is being done with the information provided ?



The first 5 questions will be posted as graphs so we have a better understanding of what type of investors we have and creating an unofficial richlist.

The paragraph text boxes will be sent to the Core dev team for fixes and understanding us better.
hero member
Activity: 798
Merit: 1000
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

What is the survey for and what is being done with the information provided ?
hero member
Activity: 565
Merit: 500
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
dga
hero member
Activity: 737
Merit: 511
Okay but I spent considerable time designing what the CryptoNote designers were attempting to design

Actually as far as I can tell, they delivered what you claim you were attempting to design. You have delivered no work product at all. No code. No white papers. Nothing. Except maybe delivered to yourself, which does not count. It is all hot air.

At this point I would ask that you take this discussion elsewhere. There may well be (theoretical, unidentified and undemonstrated) cryptographic or other issues with Cryptonight, but that is a tiny subset of topics of general interest to the user base and potential user base of Monero. Now we have the past several pages of this thread being taken over by the discussion, and the way the last few exchanges have gone, every appearance this back-and-forth will continue for several more pages. That is inappropriate. Please stop, or just go ahead and create your own thread focused on that particular subtopic.


Ah, sorry, smooth - hadn't seen this before I posted my followup.  Will stop feeding the troll on my part.
dga
hero member
Activity: 737
Merit: 511
What gives is very simple:  You're wrong;

I still believe you are wrong. See below...
...

...
The math I posted applies to any algorithm that uses randomized lookups from reading and writing to a table.

The first flaw in your analysis:  Your l3scrypt seems, from what you wrote below, to use 512b (bit?  likely, if scrypt) entries.  CryptoNight uses 128 bit entries, which means that the cost of a 24 bit counter to indicate the last-modified-in round information for a particular value is still fairly significant in comparison to the original storage.

Correct if you make your hash so slow that you can't deal with DDoS attacks (which is the case for CryptoNote), the size of the 'values' table needed to walk back each path of computation to trade computation for space, becomes larger than the space to store the values normally.

Whereas in L3crypt I have 512B entries in order to make the hash fast enough and still cover 1MB of cache to keep it in L3 cache in order to defeat economies-of-scale with Tilera cpus, GPUs, and ASICs.

So agreed CryptoNote in that case (1MB/16B table with 128-bit, i.e. 16B, elements with 1M writes) defeats the dynamic lookup gap strategy, but at the cost of making the hash too slow to defeat DDoS attacks.


Good, we're getting somewhere:  You admit that 2/3rds of your entire post doesn't apply prima facie to CryptoNote.  It might, but not with the very simple approach you claimed.  I believe you're wrong about AES as well, but I don't have time to tackle that until later today.  The 128 bit entries in CryptoNote are specifically part of what I called out earlier as a design advantage in achieving that balance.

Note carefully:  I never said CryptoNote was fast.  I never said it was a *good* choice if you are worried about DoS attacks.  I said it was a good design for balancing CPU, GPU, and ASIC computation speeds.

The reason you're wrong about GPU speeds is because the accesses saturate the memory controllers and are a poor match to the row buffer structure of DRAM, also in part due to that same 128 bit random access pattern.

So please:  Stop arguing your l3scrypt-whatever-the-fish-it-is strawman and talk about *CryptoNote as it actually exists*.


legendary
Activity: 1078
Merit: 1059
FROSTING
Fees became lower on Minergate.com!

Guys, now fees for cryptonote coins are 1.5% PPS and 1% PPLNS

2-step verification

I implemented 2 step verification, so you can protect your account with both your password and your phone. To enable it go to Dashboard - > Profile

Enjoy!

legendary
Activity: 1904
Merit: 1003
Much better than in early days when pools didn't implement minimal payout threshold.

There is no official "promise" from the development team on this, but personally I expect the on disk storage to eventually end up a closer to what is reported by monerochain.info, which means less than half of these numbers. Currently a lot of data is being stored multiple times on disk. Being smarter about how to do that should help a lot.

But first we need to get the database interface completed and a reference database integrated (see latest Missives for status). Then people can optimize.


Great, if all the dublicated data can be cut out thats good news. As said I dont see the current rate of growth as anything too troubling so with the database implemented and if anyone can optimize further it can only be positive.

At least, if there long timeframe, it's easier to implement google snappy configurable compression level. But imo it does not matter, cos it still all in RAM.
hero member
Activity: 798
Merit: 1000
Much better than in early days when pools didn't implement minimal payout threshold.

There is no official "promise" from the development team on this, but personally I expect the on disk storage to eventually end up a closer to what is reported by monerochain.info, which means less than half of these numbers. Currently a lot of data is being stored multiple times on disk. Being smarter about how to do that should help a lot.

But first we need to get the database interface completed and a reference database integrated (see latest Missives for status). Then people can optimize.


Great, if all the dublicated data can be cut out thats good news. As said I dont see the current rate of growth as anything too troubling so with the database implemented and if anyone can optimize further it can only be positive.
legendary
Activity: 2968
Merit: 1198
Much better than in early days when pools didn't implement minimal payout threshold.

There is no official "promise" from the development team on this, but personally I expect the on disk storage to eventually end up a lot closer to what is reported by monerochain.info, which means less than half of these numbers. Currently a lot of data is being stored multiple times on disk. Being smarter about how to do that should help a lot.

But first we need to get the database interface completed and a reference database integrated (see latest Missives for status). Then people can optimize.
Jump to: