A relaunch sounds reasonable, I imagine the Slimcoin dev will need to do it as quickly as possible though, make a new thread, post a link to it at the end of this thread, get this one locked, and relaunch with the fixes applied to block 16000 with a few master nodes.
Assuming you launch quickly (today if possible), the people that paid for essentially a mining farm for this coin, will not have too high of losses.
Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 95. (Read 284956 times)
June 15, 2014, 07:21:40 PM
June 15, 2014, 05:02:10 PM
Quote
Are blocks past 17000 the fix for the wallet being stuck? Or simply a high possibility? What about the blockchain getting corrupted everytime the network falls back blocks? One small error results into a big domino effect crumbling the current relative small distributed peer-to-peer network. Starting up as a decentralized network having some masternodes is a good solution to fix the sync problems when the wallet is fixed.
The origin for the blockchain forks is the PoB block discrepancies in hashes. All blocks after 17000 will be fixed of that. The blockchain corruption you talk about is not really corruption and is an easy fix, I am working on now.
It does look like a good idea to have a fair relaunch at block 16000 with a few master-nodes as currently, no one but a select few people on the correct blockchain are able to mine. Also, a relaunch would get everyone on the same place. Anyone that has comments about this, I would like to hear your ideas.
Also, adding a DNS seed node would definitely add stability to the network.
A decentralized network is just for stability until the network speed is fast enough and then it should form a distributed network. I'm willing to take part into the decentralized network, i can rent a few VPS servers running ubuntu in europe, us and asia to work as nodes with listen=1 accepting 250 connections for the first weeks.
June 15, 2014, 04:56:45 PM
When the time comes, I will host 10 or 20 supernodes, each one at a separate dedicated server. They should be able to handle/sync 5,000-10,000 clients.
June 15, 2014, 04:53:29 PM
If anyone wants to set up a DNS seed node, here is a good place to start : https://github.com/pooler/litecoin-seeder
June 15, 2014, 04:28:08 PM
We should pick a reference point closer to what the pool is at, then I will pause the pool while everyone can sync up. It's not true that only a select few people can mine, unless for solo mining. In fact most of the net hashrate is mining at the pool.
Sandor, dont be greedy, the block we agreed on is 16k. I've had my 150Kh/s pointed at the pool all day today but its just not fair to the others.
Kill the pool. Relaunch at 16k
Hey I'm not being greedy, but what about the other 52 people mining at the pool? That guy with 1Mh will be crying.
I've been yelling stop sending hash to the pool since block 15900. F... him. Only the greedy are expecting the payment. I am not and my hash was at the pool.
Fair enough. It is done.
June 15, 2014, 04:25:08 PM
We should pick a reference point closer to what the pool is at, then I will pause the pool while everyone can sync up. It's not true that only a select few people can mine, unless for solo mining. In fact most of the net hashrate is mining at the pool.
Sandor, dont be greedy, the block we agreed on is 16k. I've had my 150Kh/s pointed at the pool all day today but its just not fair to the others.
Kill the pool. Relaunch at 16k
Hey I'm not being greedy, but what about the other 52 people mining at the pool? That guy with 1Mh will be crying.
I've been yelling stop sending hash to the pool since block 15900. F... him. Only the greedy are expecting the payment. I am not and my hash was at the pool.
June 15, 2014, 04:23:09 PM
We should pick a reference point closer to what the pool is at, then I will pause the pool while everyone can sync up. It's not true that only a select few people can mine, unless for solo mining. In fact most of the net hashrate is mining at the pool.
Sandor, dont be greedy, the block we agreed on is 16k. I've had my 150Kh/s pointed at the pool all day today but its just not fair to the others.
Kill the pool. Relaunch at 16k
Hey I'm not being greedy, but what about the other 52 people mining at the pool? That guy with 1Mh will be crying.
If dev agrees on 16000, I will pause the pool.
June 15, 2014, 04:20:21 PM
We should pick a reference point closer to what the pool is at, then I will pause the pool while everyone can sync up. It's not true that only a select few people can mine, unless for solo mining. In fact most of the net hashrate is mining at the pool.
Sandor, dont be greedy, the block we agreed on is 16k. I've had my 150Kh/s pointed at the pool all day today but its just not fair to the others.
Kill the pool. Relaunch at 16k
June 15, 2014, 04:18:04 PM
Quote
Are blocks past 17000 the fix for the wallet being stuck? Or simply a high possibility? What about the blockchain getting corrupted everytime the network falls back blocks? One small error results into a big domino effect crumbling the current relative small distributed peer-to-peer network. Starting up as a decentralized network having some masternodes is a good solution to fix the sync problems when the wallet is fixed.
The origin for the blockchain forks is the PoB block discrepancies in hashes. All blocks after 17000 will be fixed of that. The blockchain corruption you talk about is not really corruption and is an easy fix, I am working on now.
It does look like a good idea to have a fair relaunch at block 16000 with a few master-nodes as currently, no one but a select few people on the correct blockchain are able to mine. Also, a relaunch would get everyone on the same place. Anyone that has comments about this, I would like to hear your ideas.
Also, adding a DNS seed node would definitely add stability to the network.
We should pick a reference point closer to what the pool is at, then I will pause the pool while everyone can sync up. It's not true that only a select few people can mine, unless for solo mining. In fact most of the net hashrate is mining at the pool.
June 15, 2014, 04:10:52 PM
Quote
Are blocks past 17000 the fix for the wallet being stuck? Or simply a high possibility? What about the blockchain getting corrupted everytime the network falls back blocks? One small error results into a big domino effect crumbling the current relative small distributed peer-to-peer network. Starting up as a decentralized network having some masternodes is a good solution to fix the sync problems when the wallet is fixed.
The origin for the blockchain forks is the PoB block discrepancies in hashes. All blocks after 17000 will be fixed of that. The blockchain corruption you talk about is not really corruption and is an easy fix, I am working on now.
It does look like a good idea to have a fair relaunch at block 16000 with a few master-nodes as currently, no one but a select few people on the correct blockchain are able to mine. Also, a relaunch would get everyone on the same place. Anyone that has comments about this, I would like to hear your ideas.
Also, adding a DNS seed node would definitely add stability to the network.
Relaunch at 16000 sounds good. I can host a DNS seed node if need be.
June 15, 2014, 04:06:10 PM
Do we lose the coins we already have if there is a relaunch?
June 15, 2014, 04:02:03 PM
Quote
Are blocks past 17000 the fix for the wallet being stuck? Or simply a high possibility? What about the blockchain getting corrupted everytime the network falls back blocks? One small error results into a big domino effect crumbling the current relative small distributed peer-to-peer network. Starting up as a decentralized network having some masternodes is a good solution to fix the sync problems when the wallet is fixed.
The origin for the blockchain forks is the PoB block discrepancies in hashes. All blocks after 17000 will be fixed of that. The blockchain corruption you talk about is not really corruption and is an easy fix, I am working on now.
It does look like a good idea to have a fair relaunch at block 16000 with a few master-nodes as currently, no one but a select few people on the correct blockchain are able to mine. Also, a relaunch would get everyone on the same place. Anyone that has comments about this, I would like to hear your ideas.
Also, adding a DNS seed node would definitely add stability to the network.
June 15, 2014, 03:36:12 PM
with 200h/s how many monero do you get per day?
With a mining difficulty of 300000000 nearly 1 XMR a day, yes the diff is high!
but the diff is even higher...
2014-Jun-15 22:54:12.010615 BH: 86883, DIFF: 410702438, HR: 6845040 H/s
look at http://pool.cryptoescrow.eu/ and see you get only 0.67 XMR with 200 h/s
June 15, 2014, 03:35:23 PM
Anyone that has had syncing issues and has investigated it, please give me your *detailed* input please.
What I have noticed is that:
PoB blocks have DoS protection that bans good nodes if too many orphan PoB blocks are sent.
PoB blocks cannot be orphaned (yet), if an orphaned PoB block is sent, it will get rejected and not recorded anywhere.
I put such DoS protection to prevent any malicious activity, but it seems it is doing more harm that good.
I do not think the issue is in the PoS blocks. As for the stop at block 16000, I will have to create a hard fork from there, that is if I see more people wanting such fork.
The intermediate burn hash fix that takes affect at block 17000 fixes: A PoB block can be falsely rejected due to inaccuracy in floating point precision between two different machines. Some nodes will accept it and others will not (and this will not be able to get to the other blocks after it). This intermediate burn hash fix, does fix this, it is not a patch.
What I have noticed is that:
PoB blocks have DoS protection that bans good nodes if too many orphan PoB blocks are sent.
PoB blocks cannot be orphaned (yet), if an orphaned PoB block is sent, it will get rejected and not recorded anywhere.
I put such DoS protection to prevent any malicious activity, but it seems it is doing more harm that good.
I do not think the issue is in the PoS blocks. As for the stop at block 16000, I will have to create a hard fork from there, that is if I see more people wanting such fork.
The intermediate burn hash fix that takes affect at block 17000 fixes: A PoB block can be falsely rejected due to inaccuracy in floating point precision between two different machines. Some nodes will accept it and others will not (and this will not be able to get to the other blocks after it). This intermediate burn hash fix, does fix this, it is not a patch.
We need an official statement about this!
Are blocks past 17000 the fix for the wallet being stuck? Or simply a high possibility? What about the blockchain getting corrupted everytime the network falls back blocks? One small error results into a big domino effect crumbling the current relative small distributed peer-to-peer network. Starting up as a decentralized network having some masternodes is a good solution to fix the sync problems when the wallet is fixed.
imo - Steps to take:
After the official statement work to be done something like this
1) Fix the wallet - is the 17000+ block enough?
2) Setup 6 master nodes on test network
3) Setup 3 seed nodes on test network
4) Alter OP topic with addnodes to the master nodes
5) Switch nodes to normal network and make it a fair relaunch at block 16000 - instruct pool owners
PS: Let others setup some master nodes until the network speed is secure, write a guide
June 15, 2014, 03:30:14 PM
with 200h/s how many monero do you get per day?
June 15, 2014, 03:23:53 PM
are there any working nodes right now?
i have no idea at the moment, will see tomorrow.. currently my wallets are down and i'm mining monero with gpu and cpu
but the pool isn't really "instamine".. even thru it finds almost all blocks because it's the only one in the front of the chain..
the block target of 90 seconds is in place
What speeds would you say a 7950 could pull with monero...I'm getting about 25-30 h/s with my cpu
i think it will do ~200 h/s, but that is just a suggestion. And it seems your cpu is slow
My 4770 does ~200 h/s June 15, 2014, 02:33:07 PM
are there any working nodes right now?
i have no idea at the moment, will see tomorrow.. currently my wallets are down and i'm mining monero with gpu and cpu
but the pool isn't really "instamine".. even thru it finds almost all blocks because it's the only one in the front of the chain..
the block target of 90 seconds is in place
What speeds would you say a 7950 could pull with monero...I'm getting about 25-30 h/s with my cpu
June 15, 2014, 01:54:52 PM
are there any working nodes right now?
i have no idea at the moment, will see tomorrow.. currently my wallets are down and i'm mining monero with gpu and cpu
but the pool isn't really "instamine".. even thru it finds almost all blocks because it's the only one in the front of the chain..
the block target of 90 seconds is in place
June 15, 2014, 01:46:51 PM
are there any working nodes right now?
June 15, 2014, 01:13:51 PM
Today is holiday so everyone's taking a break. sandor111 is no where to find. Happy instamining, dude. I'm out.
Jump to: