|
Rias
|
 |
June 20, 2014, 11:19:44 AM |
|
Let me break this down for you:
1) Top EC2 instance has around 700 hash/sec. -- Wrong 2) Each of the instances costs more than $1000 per month ($33 per day) -- Wrong 3) It's very unlikely that it could happen in 2 days. -- Wrong
Your math may be right, but your inputs are all wrong. Botnets can't come anywhere near EC2.
Let's check. http://aws.amazon.com/ec2/pricing/c3.8xlarge is $1.680 per Hour, which is $40 per day. Sorry, I was all wrong, it's even worse than I was writing. 3) It's very unlikely that it could happen in 2 days. -- Wrong It would be a nightmare to get the limit and set up 2,800 servers. Is there a shortcut?
|
|
|
|
|
|
onemorebtc
|
 |
June 20, 2014, 11:20:52 AM |
|
This can be crucial for the exchanges and pools. What if a user withdraws the money and it got stuck and reversed after 24 hours?
If you are right, I assume the service gets the transaction back without any notification about that. Suddenly, there is simply money on the wallet with no other information on the transfer. So the service will have to manually recalculate all the incoming and outgoing transactions to test, who is the transaction owner. The larger your service, the more useless work you should be doing on the daily bases.
That's not too friendly towards the businesses working with Monero for sure.
and whats the differnce with ANY other crypto? you'll send a transaction and check if the network accepts it... if not you rebroadcast or doublespent it with a higher fee (the last one only works with btc and eligius - afaik) It's a different approach. The service should be notified when the transaction is reversed, otherwise it breaks whole user experience. The money were withdrawn, never appeared in the user's wallet and are not identified by the service and couldn't be credited back to the account. ok... just write a script that checks if a transaction has gone through and execute it regulary? btw: do you know that a reverse can be reversed to? if the client did already notify the service it would have been resent... orphan blocks can be the realchain again: they just need a miner who builds on them (and this can happen very fast)
|
transfer 3 onemorebtc.k1024.de 1
|
|
|
|
Hexah
|
 |
June 20, 2014, 11:21:07 AM |
|
Let's do the math.
Top EC2 instance has around 700 hash/sec. One added instance is likely to have 42,000 difficulty increase. To get 100,000,000 difficulty increase you'd have to add 2,380 of top EC2 instance. Each of the instances costs more than $1000 per month ($33 per day) and requires some work to increase the limits on your account and prepare the servers for mining.
Not only I don't believe someone invest $80,000 a day to mine XMR, it's very unlikely that it could happen in 2 days.
Let me break this down for you: 1) Top EC2 instance has around 700 hash/sec. -- Wrong 2) Each of the instances costs more than $1000 per month ($33 per day) -- Wrong 3) It's very unlikely that it could happen in 2 days. -- Wrong Your math may be right, but your inputs are all wrong. Botnets can't come anywhere near EC2. Would you be so kind to provide the proof? I've been mining on c3.8xlarge myself. What's your inputs than? you contradict yourself: i dont like botnets and think they are criminal. but i dont really see an issue from a crypto-currency-user perspective
edit: botnets dont havy any influence about how many new coins where generated per day. just how much other miners get
Exactly and in my opinion it is way worse than coins in the hands of the devs. Which is not the case for BCN with several hundreds of early miners identified. This can be crucial for the exchanges and pools. What if a user withdraws the money and it got stuck and reversed after 24 hours?
If you are right, I assume the service gets the transaction back without any notification about that. Suddenly, there is simply money on the wallet with no other information on the transfer. So the service will have to manually recalculate all the incoming and outgoing transactions to test, who is the transaction owner. The larger your service, the more useless work you should be doing on the daily bases.
That's not too friendly towards the businesses working with Monero for sure.
Exactly. Monero developers are clearly not qualified enough for this yet. Monero is moving in a completely wrong direction. i2p integration, for instance, is nonsense. I remember some guy in twitter was not satisfied with Monero developers either. Well, not some regular guy but some big Bitcoin programmer / enthusiast can’t remember his name. UPD: found him https://twitter.com/lopp/status/472359052736204800
|
|
|
|
|
|
HardwarePal
|
 |
June 20, 2014, 11:26:24 AM |
|
Rias all your posts are in the BCN thread . Why would someone believe you are not one of the people behind the 80% instamine before the public release of Bytecoin. Please man if your going to FUD like this do it professionally at least Theres better ways to lead people into Bytecoin and dump in there faces
|
|
|
|
|
|
equipoise
|
 |
June 20, 2014, 11:27:15 AM |
|
Two pages of troll posts. They should be scared.
|
|
|
|
|
HardwarePal
|
 |
June 20, 2014, 11:29:38 AM |
|
Two pages of troll posts. They should be scared.
Well you know what they say when fudders and trolls join a coins ann thread  Good luck to BCN but no thanks I prefer XMR 
|
|
|
|
|
|
Rias
|
 |
June 20, 2014, 11:30:56 AM |
|
Rias all your posts are in the BCN thread . Why would someone believe you are not one of the people behind the 80% instamine before the public release of Bytecoin. Please man if your going to FUD like this do it professionally at least Theres better ways to lead people into Bytecoin and dump in there faces I'm not fudding, I'm raising concerns. Grounded concerns, if you don't mind. And XMR developers should better take it very seriously. I really like it how people not knowing a damn about the technology judge whether my arguments are correct or not. Ok, XMR sock puppets have arrived, I'm going home.
|
|
|
|
|
|
HardwarePal
|
 |
June 20, 2014, 11:33:28 AM |
|
Rias all your posts are in the BCN thread . Why would someone believe you are not one of the people behind the 80% instamine before the public release of Bytecoin. Please man if your going to FUD like this do it professionally at least Theres better ways to lead people into Bytecoin and dump in there faces I'm not fudding, I'm raising concerns. Grounded concerns, if you don't mind. And XMR developers should better take it very seriously. I really like it how people not knowing a damn about the technology judge whether my arguments are correct or not. Ok, XMR sock puppets have arrived, I'm going home. No need to keep spamming the thread, they will answer soon enough I guess
|
|
|
|
|
|
Hexah
|
 |
June 20, 2014, 11:33:59 AM |
|
Two pages of troll posts. They should be scared.
Usual monero-tactics for "do xmr devs really develop smth?" topics: just change the subject to "troll FUD" and ignore all the arguments
|
|
|
|
|
|
DLow
|
 |
June 20, 2014, 11:34:50 AM |
|
Hey,
would it be possible to implement a "Zero Transactions" function for the pools?
So one can reset the "Total Paid"? I like to keep tabs about my daily mining efforts and such.
|
|
|
|
|
CarlesPuyol
Legendary

Activity: 1148
Merit: 1000
|
 |
June 20, 2014, 11:41:03 AM |
|
the XMR progress is great, looks promising for the short time - will enter to Mintpal at monday and now its a great enter point. will cross the 1 milion satoshi.
|
|
|
|
|
|
1qaz
|
 |
June 20, 2014, 11:43:04 AM |
|
|
|
|
|
|
|
HardwarePal
|
 |
June 20, 2014, 11:46:48 AM |
|
Two pages of troll posts. They should be scared.
Usual monero-tactics for "do xmr devs really develop smth?" topics: just change the subject to "troll FUD" and ignore all the arguments Let them log on and they will quote your questions imo
|
|
|
|
|
|
novag
|
 |
June 20, 2014, 12:12:44 PM |
|
Maybe need waiting some time.
|
Donate for the support of a new Martial arts Style - Aikivindo = Aikido + Wing-Chun (in Ukraine) 5168757318423326 PrivatBank. http://aikivindo.com.uaBTC:1DpRaQjdVmrkSopRV8p9RdwvBMWNA9faCS
|
|
|
GreekBitcoin
Legendary

Activity: 1428
Merit: 1001
getmonero.org
|
 |
June 20, 2014, 12:14:35 PM |
|
So Rias if i understand correctly that means that not even botnets care about bytecoin because with the 80% premine there is nothing but constant dumping? You tend to forget also all the gpus starting mining now that darkcoin is dropping...More and more people starting learning about the coin... And yes some serious investors that could never invest 80k for a 80% premined coin...
Also Hexah i thought that bytecoin devs are anonymous. Meanwhile at least 4 of the main devs of monero arent as far as i know. This has been answered again many many pages before...
And finally, better in the wrong direction than 0 direction at all. Let us (community) choose which is the right direction. For now it seems the wrong direction was the 80% premine of BCN and the 0 community and updates for the alleged two years of existence...
Why dont you go back and circlejerk on your BCN thread and "wow omg such great website and forum" ?
|
|
|
|
|
Matt9301
Legendary

Activity: 1652
Merit: 1009
|
 |
June 20, 2014, 12:19:54 PM |
|
GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 06/20/14-14:18:39 - SHARE FOUND (target 25000) - (GPU 0) GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 Error in server response : {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Lowdifficultyshare"}}
Stratum - connecting to 'monero.crypto-pool.fr' <62.210.78.186> port 6666 GPU 0, GpuMiner k1a failed -55 Stratum - Connected Pool Diff 25000.1 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 I receive this error with gpu miner, anyone can help me??
|
|
|
|
|
|
othe
|
 |
June 20, 2014, 12:21:19 PM |
|
Come on, give Monero guys some credit. They are maintaining the biggest CryptoNote community there is and doing it pretty well.
Maintaining community is one thing and developing an innovative tech is another. I really appreciate what XMR does to CryptoNote promotion and development of pools, wallets, etc. However, if you take a look at their recent transaction pool changes, you'll be quite surprised. Firstly, Monero devs changed the source code so that the transactions could stay in pools forever. This lead to transaction piling up to 250+ transactions in the daemon tx_pools, which were not going anywhere at all and could be stuck for eternity. Secondly, they took BBR solution to the problem and I assume didn't even bother thinking deeply on what they were adding. The 24h limit for transactions in the pool was a solution but again not a wise one. As there are no wallet notifications, the wallet doesn't know anything about the transactions being reversed. Users, services are not notified on the process at all. What's more, if there are older daemons in the network, a more interesting case is possible. The transaction is reversed in newer daemons, the inputs are free again for other transactions. But when they're used, the older daemons (which didn't get the transaction out of their tx_pools) have to report double-spending attempts. This is not how you make critical updates for the currency. 1) Monero developers should evaluate the long term consequences of their commits. Each unthought solution can cause drastic problems in the long run. 2) Monero developers should allow a compatibility window in order to make sure that the network is not split during the update. It's not about "mandatory update" alert on the forum, but a sophisticated approach inside the source code. And that is why I prefer Bytecoin developers approach. I'm sure they can't ruin the network with one random commit. Can't say the same about XMR devs. Its friday and i have really better things todo than addressing your constant hate without a reason. First of all, it was a hotfix and its was coordinated with pools and exchanges, there is absolutely no problem users just need to update their wallets... Polo and Bittrex both work pretty close with us and we coordinate everything with them. There was nothing uncoordinated i have even discussed the fix with zoidberg and he sees no problem either. There was a compatibility window and still is - there are pools who mine the low fee transactions. About the hashrate and your botnet paranoia - the hashincrease simply matches the price increase on exchanges, theres no vodoo or black magic - and whats the difference to BCN, they use the same Proof of work... Then your other concern that the miner was crippled is just a joke because we were the ones who fixed it, you better ask bcn why they did make the pow so slow without a reason. The dev progress speaks to itself, you just have to check our githubs (all monero people): https://github.com/mikezackles/bitmonero/commits/daemonizehttps://github.com/Neozaru/bitmonero/commits/masterhttps://github.com/wolf9466/bitmonero/commits/masterhttps://github.com/wolf9466/cpuminer-multi/commits/masterhttps://github.com/fluffypony/bitmonero/commits/masterhttps://github.com/tewinget/bitmonero/commits/masterhttps://github.com/zone117x/node-cryptonote-pool/commits/masterhttps://github.com/NoodleDoodleNoodleDoodleNoodleDoodleNoo/bitmonero/commits/masterThis is an open source project with a great community and not a one man show, you should realize that. And that is why I prefer Bytecoin developers approach. I'm sure they can't ruin the network with one random commit. Can't say the same about XMR devs. There was a critical bug which allowed the blockchain to be replaced due to an error in their checkpoint system we found here: https://github.com/monero-project/bitmonero/commit/5ceffa8c8abb96bb8314939bf75c9b935ea7b5bcand fixed here: https://github.com/monero-project/bitmonero/commit/e7171250739790a5e5040264c4c1356ddeeea241This bug allowed it to replace the whole blockchain on CN coins, because it made it possible to fabricate a blockchain with a bigger cummulative difficulty due to non-checking of the block before the checkpointing. Just for your info. Ultimately we should all work together but with the hatred from certain people here i doubt that will happen....
|
|
|
|
|
HardwarePal
|
 |
June 20, 2014, 12:21:53 PM |
|
GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 06/20/14-14:18:39 - SHARE FOUND (target 25000) - (GPU 0) GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 Error in server response : {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Lowdifficultyshare"}}
Stratum - connecting to 'monero.crypto-pool.fr' <62.210.78.186> port 6666 GPU 0, GpuMiner k1a failed -55 Stratum - Connected Pool Diff 25000.1 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 I receive this error with gpu miner, anyone can help me?? Try Claymores thread here : https://bitcointalk.org/index.php?topic=638915.0Someone will help you out Edited Link was wrong
|
|
|
|
|
Matt9301
Legendary

Activity: 1652
Merit: 1009
|
 |
June 20, 2014, 12:26:10 PM |
|
GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 06/20/14-14:18:39 - SHARE FOUND (target 25000) - (GPU 0) GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 Error in server response : {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Lowdifficultyshare"}}
Stratum - connecting to 'monero.crypto-pool.fr' <62.210.78.186> port 6666 GPU 0, GpuMiner k1a failed -55 Stratum - Connected Pool Diff 25000.1 GPU 0, GpuMiner k1a failed -55 GPU 0, GpuMiner k1a failed -55 I receive this error with gpu miner, anyone can help me?? Try Claymores thread here : https://bitcointalk.org/index.php?topic=638915.0Someone will help you out Edited Link was wrong Thank you bro!
|
|
|
|
|
|
darkota
|
 |
June 20, 2014, 12:38:44 PM |
|
Come on, give Monero guys some credit. They are maintaining the biggest CryptoNote community there is and doing it pretty well.
Maintaining community is one thing and developing an innovative tech is another. I really appreciate what XMR does to CryptoNote promotion and development of pools, wallets, etc. However, if you take a look at their recent transaction pool changes, you'll be quite surprised. Firstly, Monero devs changed the source code so that the transactions could stay in pools forever. This lead to transaction piling up to 250+ transactions in the daemon tx_pools, which were not going anywhere at all and could be stuck for eternity. Secondly, they took BBR solution to the problem and I assume didn't even bother thinking deeply on what they were adding. The 24h limit for transactions in the pool was a solution but again not a wise one. As there are no wallet notifications, the wallet doesn't know anything about the transactions being reversed. Users, services are not notified on the process at all. What's more, if there are older daemons in the network, a more interesting case is possible. The transaction is reversed in newer daemons, the inputs are free again for other transactions. But when they're used, the older daemons (which didn't get the transaction out of their tx_pools) have to report double-spending attempts. This is not how you make critical updates for the currency. 1) Monero developers should evaluate the long term consequences of their commits. Each unthought solution can cause drastic problems in the long run. 2) Monero developers should allow a compatibility window in order to make sure that the network is not split during the update. It's not about "mandatory update" alert on the forum, but a sophisticated approach inside the source code. And that is why I prefer Bytecoin developers approach. I'm sure they can't ruin the network with one random commit. Can't say the same about XMR devs. Its friday and i have really better things todo than addressing your constant hate without a reason. First of all, it was a hotfix and its was coordinated with pools and exchanges, there is absolutely no problem users just need to update their wallets... Polo and Bittrex both work pretty close with us and we coordinate everything with them. There was nothing uncoordinated i have even discussed the fix with zoidberg and he sees no problem either. There was a compatibility window and still is - there are pools who mine the low fee transactions. About the hashrate and your botnet paranoia - the hashincrease simply matches the price increase on exchanges, theres no vodoo or black magic - and whats the difference to BCN, they use the same Proof of work... Then your other concern that the miner was crippled is just a joke because we were the ones who fixed it, you better ask bcn why they did make the pow so slow without a reason. The dev progress speaks to itself, you just have to check our githubs (all monero people): https://github.com/mikezackles/bitmonero/commits/daemonizehttps://github.com/Neozaru/bitmonero/commits/masterhttps://github.com/wolf9466/bitmonero/commits/masterhttps://github.com/wolf9466/cpuminer-multi/commits/masterhttps://github.com/fluffypony/bitmonero/commits/masterhttps://github.com/tewinget/bitmonero/commits/masterhttps://github.com/zone117x/node-cryptonote-pool/commits/masterhttps://github.com/NoodleDoodleNoodleDoodleNoodleDoodleNoo/bitmonero/commits/masterThis is an open source project with a great community and not a one man show, you should realize that. And that is why I prefer Bytecoin developers approach. I'm sure they can't ruin the network with one random commit. Can't say the same about XMR devs. There was a critical bug which allowed the blockchain to be replaced due to an error in their checkpoint system we found here: https://github.com/monero-project/bitmonero/commit/5ceffa8c8abb96bb8314939bf75c9b935ea7b5bcand fixed here: https://github.com/monero-project/bitmonero/commit/e7171250739790a5e5040264c4c1356ddeeea241This bug allowed it to replace the whole blockchain on CN coins, because it made it possible to fabricate a blockchain with a bigger cummulative difficulty due to non-checking of the block before the checkpointing. Just for your info. Ultimately we should all work together but with the hatred from certain people here i doubt that will happen.... Wow, very impressive I must say, thanks for fixing that bug. I'm setting aside 10% of income from trading to make a developers fund atm.
|
|
|
|
|
|