Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1778. (Read 4670606 times)
Monero is at .0062, I feel like slapping myself. Wish I had bought some more earlier..I only have 20 moneros.. ):
Out of interest, does monero fork as I haven't read anything about it yet... Or is it immune to this problem ?
There was a risk of fork at the very beginning that has been solved quickly.
Nothing since.
Does that mean it is immune to it or does a fork just happen at random times? I was just reading the DRK thread and they saying there is a fork again... but what would make people sell thier DRK when there is a fork? The wallet just needs updating and all will be fine ?
Darkcoin just forks because they added changes on the protocol level that a soft-update isn't enough for.
And yes if a coin hardforks every user needs to update their wallet/daemon, if you coordinate that ok it isnt much of an issue.
Dont mix this up with "network forking" where multiple blockchains exists.
But lets keep this topic monero only please, there are enough threads for all other coins.
Out of interest, does monero fork as I haven't read anything about it yet... Or is it immune to this problem ?
There was a risk of fork at the very beginning that has been solved quickly.
Nothing since.
Does that mean it is immune to it or does a fork just happen at random times? I was just reading the DRK thread and they saying there is a fork again... but what would make people sell thier DRK when there is a fork? The wallet just needs updating and all will be fine ?
You shouldn't informe yourself about a currencyin a others currency thread lel. That's like asikng a Google employee if Bing is hood or asking Tim Cook if Windows 8 is superior
Out of interest, does monero fork as I haven't read anything about it yet... Or is it immune to this problem ?
There was a risk of fork at the very beginning that has been solved quickly.
Nothing since.
Does that mean it is immune to it or does a fork just happen at random times? I was just reading the DRK thread and they saying there is a fork again... but what would make people sell thier DRK when there is a fork? The wallet just needs updating and all will be fine ?
Out of interest, does monero fork as I haven't read anything about it yet... Or is it immune to this problem ?
There was a risk of fork at the very beginning that has been solved quickly.
Nothing since.
Out of interest, does monero fork as I haven't read anything about it yet... Or is it immune to this problem ?
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/daemonize
https://github.com/Neozaru/bitmonero/commits/master
https://github.com/wolf9466/bitmonero/commits/master
https://github.com/wolf9466/cpuminer-multi/commits/master
https://github.com/fluffypony/bitmonero/commits/master
https://github.com/tewinget/bitmonero/commits/master
https://github.com/zone117x/node-cryptonote-pool/commits/master
https://github.com/NoodleDoodleNoodleDoodleNoodleDoodleNoo/bitmonero/commits/master
This is an open source project with a great community and not a one man show, you should realize that.
Quote
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/5ceffa8c8abb96bb8314939bf75c9b935ea7b5bc
and fixed here: https://github.com/monero-project/bitmonero/commit/e7171250739790a5e5040264c4c1356ddeeea241
This 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.
Quote
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
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://bitcointalksearch.org/topic/claymores-cryptonote-amd-gpu-miner-v113-638915
Someone will help you out
Edited Link was wrong
Thank you bro!
Quote
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
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://bitcointalksearch.org/topic/claymores-cryptonote-amd-gpu-miner-v113-638915
Someone will help you out
Edited Link was wrong
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/daemonize
https://github.com/Neozaru/bitmonero/commits/master
https://github.com/wolf9466/bitmonero/commits/master
https://github.com/wolf9466/cpuminer-multi/commits/master
https://github.com/fluffypony/bitmonero/commits/master
https://github.com/tewinget/bitmonero/commits/master
https://github.com/zone117x/node-cryptonote-pool/commits/master
https://github.com/NoodleDoodleNoodleDoodleNoodleDoodleNoo/bitmonero/commits/master
This is an open source project with a great community and not a one man show, you should realize that.
Quote
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/5ceffa8c8abb96bb8314939bf75c9b935ea7b5bc
and fixed here: https://github.com/monero-project/bitmonero/commit/e7171250739790a5e5040264c4c1356ddeeea241
This 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....
Quote
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
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??
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" ?
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" ?
Maybe need waiting some time.
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
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.
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.
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.
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
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
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
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
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.
Jump to: