We can do it ! Go go go 8-bit-Party !
https://www.youtube.com/watch?v=HVgoudZxCB8&feature=youtu.be
Topic: [*] 8BIT [Dark Masternodes][Anon][Roadmap Stage 4] - page 60. (Read 379550 times)
I have a problem to send mp... 
try to send mp to gerry for the slack invit
try to send mp to gerry for the slack invit
Hi all. I'm back. so using the plan i outlined above, i did indeed run into orphaned blocks and couldn't get past block 517,624 (1 year 5 weeks remaining.). i used the following nodes as connect:
connect=91.121.79.208
connect=45.32.207.94
connect=144.76.115.195
connect=194.60.247.77
connect=118.102.74.85
connect=188.244.136.3
connect=92.54.74.91
connect=188.244.136.3
connect=94.226.187.230
connect=94.225.84.218
connect=188.244.136
connect=92.222.68.70
connect=217.182.173.89
connect=217.96.23.2
connect=184.89.70.195
so either 1) one or more of the connects above are invalid
or 2) the Block.tgz is in valid.
connect=91.121.79.208
connect=45.32.207.94
connect=144.76.115.195
connect=194.60.247.77
connect=118.102.74.85
connect=188.244.136.3
connect=92.54.74.91
connect=188.244.136.3
connect=94.226.187.230
connect=94.225.84.218
connect=188.244.136
connect=92.222.68.70
connect=217.182.173.89
connect=217.96.23.2
connect=184.89.70.195
so either 1) one or more of the connects above are invalid
or 2) the Block.tgz is in valid.
Nonononono. Please follow this approach:
1. Remove database/ txleveldb/ blk0001.dat from your wallet directory
2. Download blocks.tgz from http://www.8-bit.ga/#download
3. Extract blocks.tgz in your wallet directory (so you will have a new database/ txleveldb/ blk0001.dat created there)
4. Remove all addnode / connect entries from your 8bit.conf and add following:
Code:
connect=node00.8-bit.ga
connect=node01.8-bit.ga
connect=node02.8-bit.ga
connect=node03.8-bit.ga
connect=node04.8-bit.ga
connect=node05.8-bit.ga
connect=node01.8-bit.ga
connect=node02.8-bit.ga
connect=node03.8-bit.ga
connect=node04.8-bit.ga
connect=node05.8-bit.ga
5. Run your 8bit wallet with -rescan switch
6. Enjoy the blockchain. At least as long as will not make a surprise
either way, this coin won't get anywhere until this is straighten out.
i'm calling for the community to work together and fix this. - p.s. forget about bittrex and exchanges, you have a core problem here.
It will be never fixed as even if, blockchain is too bloated to be still used. Start from scratch will happen.i'm calling for the community to work together and fix this. - p.s. forget about bittrex and exchanges, you have a core problem here.
When will the start from scratch happenn? Assumming the problem is still persisting to date.
Yes, masternodes work perfectly on Linux (Ubuntu in particular). Not sure there are instructions for this coin, but the process is the same as most other masternode coins, aka Dash or BitSend. The collateral is 112 8BIT, thats the only difference.
Also, masternode.conf cannot be used with the current source, but that is easily fixable, if anyone needs, I can send the instructions to patch the source.
Heh, to write good instructions, I have to spend a lot of time, which I don't have unfortunately. To write bad instructions, I need much less time, but I don't want to write bad instructions.
However here is a good guide here for setting up ChainCoin masternodes: http://chaincoin.org/Setting%20up%20a%20Chaincoin%20Masternode%20-%20draft%20v.04.pdf
It is too detailed to my taste, but is a nice one. With some understanding, you can follow it, while replacing ChainCoin with 8bit where needed. Or just read it, to get an idea on what needs to be done. The first part (setting up a VPS) is completely generic, and can be followed blindly. The second part - needs to be adopted for 8bit. Volunteers welcome.
thanks, I was referring to if you could send the instructions to patch the source
The configuration of the generic mastery that I know, but what I asked for is what you offered previously
Sure. Will send it tomorrow (its late night here, and I am not at my pc). Remember - this little source patch is only needed to be able to run many masternodes at once using "masternode.conf". I suppose you should already know how to use masternode.conf, so will just send the small code patch.
Still waiting for the patch to run multiple masternodes on Ubuntu. It would be perfect if you can just mention the simplified version of the instructions for complete beginners like me, that have already read tutorials about masternodes but might encounter dificulties setting it up for 8bit.
How to mine it? There are no instructions at all on the website or first post.
Used the bootstrap and nodes specificed that are working, but I'm stuck at block 974632
My log file currently looks like this (last few lines):
ProcessBlock: ORPHAN BLOCK 57, prev=5d287216797d200819c6b63735f9016b5446b47a44ec71a965a08d1911269051
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 94.226.187.230:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
SetBestChain: new best=5fb1dcb3f7d70cf54c7e6151caa62e4752ffc6f9cc72ea06ae906c211c84a635 height=974633 trust=30895760552085056363 blocktrust=4042435328510 date=07/15/17 14:04:32
ProcessBlock: ACCEPTED
ProcessBlock: ORPHAN BLOCK 58, prev=57260aa1549d6e20608ed6b5608ae48e0a14a4ee8a767d492d66eb3333952321
ProcessBlock: ORPHAN BLOCK 59, prev=6936f293a6114427625f4d6d5d2e6cb0449f423b9d9fed22904b91c8c0104977
connect() to 46.101.206.55:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 213.249.13.246:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
Anything I can do here?
My log file currently looks like this (last few lines):
ProcessBlock: ORPHAN BLOCK 57, prev=5d287216797d200819c6b63735f9016b5446b47a44ec71a965a08d1911269051
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 94.226.187.230:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
SetBestChain: new best=5fb1dcb3f7d70cf54c7e6151caa62e4752ffc6f9cc72ea06ae906c211c84a635 height=974633 trust=30895760552085056363 blocktrust=4042435328510 date=07/15/17 14:04:32
ProcessBlock: ACCEPTED
ProcessBlock: ORPHAN BLOCK 58, prev=57260aa1549d6e20608ed6b5608ae48e0a14a4ee8a767d492d66eb3333952321
ProcessBlock: ORPHAN BLOCK 59, prev=6936f293a6114427625f4d6d5d2e6cb0449f423b9d9fed22904b91c8c0104977
connect() to 46.101.206.55:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 213.249.13.246:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
Anything I can do here?
I am running a linux wallet, but how do you tell when it's sync'ed?
where can i see the latest block?
where can i see the latest block?
Current block number is: 979204
wallet syncing is taking forever how do i fix this still 1 year and 48 weeks to go ??
The snapshot of the blockchain that shared drays, plus their masternodes as a source, allowed me to sync my wallet
finaly this worked thanks alot guys
Interesting price for a masternode. However, I am not able to find a working download for the wallet on windows.
I am running a linux wallet, but how do you tell when it's sync'ed?
where can i see the latest block?
where can i see the latest block?
Will wait until all sorted before investing in few MNS
Makes sense.There was someone rumouring the MN will go from 112 to 1024 coins. Can you confirm or deny this?
wallet syncing is taking forever how do i fix this still 1 year and 48 weeks to go ??
The snapshot of the blockchain that shared drays, plus their masternodes as a source, allowed me to sync my wallet
Will wait until all sorted before investing in few MNS
Makes sense.wallet syncing is taking forever how do i fix this still 1 year and 48 weeks to go ??
Wait for bootstrap / parsed chain / code rebase & chain swap.First two options coming soon.
Will wait until all sorted before investing in few MNS
isnt that a big problem? seems lke a major problem.
how come there are two chains? longer and shorter
lets say bittrex has the only real chain.
arent all blocks after bittrex last block no valid, because it never existed on that chain.
at some point those two chains got split?
how can any block after the split be valid?
so even if cryptopia is on the right chain, there shouldnt be any bittrex transactions inside of it.
or does only bittrex not have crytopia transactions?
how come there are two chains? longer and shorter
lets say bittrex has the only real chain.
arent all blocks after bittrex last block no valid, because it never existed on that chain.
at some point those two chains got split?
how can any block after the split be valid?
so even if cryptopia is on the right chain, there shouldnt be any bittrex transactions inside of it.
or does only bittrex not have crytopia transactions?
https://en.bitcoin.it/wiki/Block_chain
wallet syncing is taking forever how do i fix this still 1 year and 48 weeks to go ??
Nice movement here, really nice.
Anyway, as stated, Bittrex is on shorter chain, Cryptopia is PROBABLY on longest one. I am saying PROBABLY because they no longer display block height and therefore we do not know where they are anymore
Once I will make sure that Cryptopia is on the right chain I will:
1) update seed nodes
2) refresh block explorer
3) send parsed chain to the website & make sure Bittrex got it
Props for drays for sharing the longest chain files.
There was not attack whatsoever, neither this time nor ever before.
Anyway, as stated, Bittrex is on shorter chain, Cryptopia is PROBABLY on longest one. I am saying PROBABLY because they no longer display block height and therefore we do not know where they are anymore
Once I will make sure that Cryptopia is on the right chain I will:
1) update seed nodes
2) refresh block explorer
3) send parsed chain to the website & make sure Bittrex got it
Props for drays for sharing the longest chain files.
There was not attack whatsoever, neither this time nor ever before.
I can confirm that cryptopia is in the longest chain, today I received my coins using the masternodes of Drays:
Addnode = 91.121.79.208
Addnode = 104.207.131.249
Addnode = 184.164.129.202
Addnode = 136.243.147.46
Addnode = 144.76.115.195
Addnode = 136.243.147.46
Addnode = 136.243.147.46
Addnode = 197.231.221.211
Addnode = 136.243.147.46
Addnode = 85.10.199.167
Addnode = 136.243.147.46
Addnode = 5.141.198.37
Addnode = 136.243.147.46
Addnode = 207.138.200.254
Addnode = 91.10.24.229
Addnode = 85.10.199.167
Addnode = 46.101.15.38
Addnode = 136.243.147.46
Addnode = 98.14.211.131
Addnode = 136.243.147.46
These are in the same chain as the cryptopia osea long chain. I'll buy coins again for another node
Nice movement here, really nice.
Anyway, as stated, Bittrex is on shorter chain, Cryptopia is PROBABLY on longest one. I am saying PROBABLY because they no longer display block height and therefore we do not know where they are anymore
Once I will make sure that Cryptopia is on the right chain I will:
1) update seed nodes
2) refresh block explorer
3) send parsed chain to the website & make sure Bittrex got it
Props for drays for sharing the longest chain files.
There was not attack whatsoever, neither this time nor ever before.
Anyway, as stated, Bittrex is on shorter chain, Cryptopia is PROBABLY on longest one. I am saying PROBABLY because they no longer display block height and therefore we do not know where they are anymore
Once I will make sure that Cryptopia is on the right chain I will:
1) update seed nodes
2) refresh block explorer
3) send parsed chain to the website & make sure Bittrex got it
Props for drays for sharing the longest chain files.
There was not attack whatsoever, neither this time nor ever before.
isnt that a big problem? seems lke a major problem.
how come there are two chains? longer and shorter
lets say bittrex has the only real chain.
arent all blocks after bittrex last block no valid, because it never existed on that chain.
at some point those two chains got split?
how can any block after the split be valid?
so even if cryptopia is on the right chain, there shouldnt be any bittrex transactions inside of it.
or does only bittrex not have crytopia transactions?
Nice movement here, really nice.
Anyway, as stated, Bittrex is on shorter chain, Cryptopia is PROBABLY on longest one. I am saying PROBABLY because they no longer display block height and therefore we do not know where they are anymore
Once I will make sure that Cryptopia is on the right chain I will:
1) update seed nodes
2) refresh block explorer
3) send parsed chain to the website & make sure Bittrex got it
Props for drays for sharing the longest chain files.
There was not attack whatsoever, neither this time nor ever before.
Anyway, as stated, Bittrex is on shorter chain, Cryptopia is PROBABLY on longest one. I am saying PROBABLY because they no longer display block height and therefore we do not know where they are anymore
Once I will make sure that Cryptopia is on the right chain I will:
1) update seed nodes
2) refresh block explorer
3) send parsed chain to the website & make sure Bittrex got it
Props for drays for sharing the longest chain files.
There was not attack whatsoever, neither this time nor ever before.
Jump to: