Pages:
Author

Topic: [ANN][BEL][Digishield] BELLS Dev. by BillyM2k(Dogecoin dev)Forked, Fast, Fun! - page 3. (Read 63135 times)

full member
Activity: 243
Merit: 100
Any chance you have the blockchain still? Maybe put it onto the network, I've added the nodes.

I used to have a crapload, but now I'm sure my wallet is like 200k, anyways, could probably put half that into someone willing to revive this coin.

203.20.114.252 is up again, and I can see a new peer starting from height 0... Smiley

I'm up to 240,000+ blocks.

Did you ever get fully synced?

Not sure I needed to 'fully sync' - I first started with BEL in 2014 so it's more likely that the network was active, then everyone slowly dropped off, and I ended up being the last one running a client (at least, one with a global listening port).

The trouble with a fledgling or dying network is that it's easier to split, with two halves unaware of each other, each side extending their own fork of the original chain. I have no idea if someone else continued mining with another random peer at some point after I lost my last connection.

How about we kick start this? My mining system is ignoring the coin because the last block was too long ago, but a single block will get it noticed again. Smiley

Well it's moving again. Not sure who is mining, I tried today with my CPU but didn't get anything.

Local Block Explorer screenshot


legendary
Activity: 2268
Merit: 1092
Any chance you have the blockchain still? Maybe put it onto the network, I've added the nodes.

I used to have a crapload, but now I'm sure my wallet is like 200k, anyways, could probably put half that into someone willing to revive this coin.

203.20.114.252 is up again, and I can see a new peer starting from height 0... Smiley

I'm up to 240,000+ blocks.

Did you ever get fully synced?

Not sure I needed to 'fully sync' - I first started with BEL in 2014 so it's more likely that the network was active, then everyone slowly dropped off, and I ended up being the last one running a client (at least, one with a global listening port).

The trouble with a fledgling or dying network is that it's easier to split, with two halves unaware of each other, each side extending their own fork of the original chain. I have no idea if someone else continued mining with another random peer at some point after I lost my last connection.

How about we kick start this? My mining system is ignoring the coin because the last block was too long ago, but a single block will get it noticed again. Smiley
full member
Activity: 243
Merit: 100
Any chance you have the blockchain still? Maybe put it onto the network, I've added the nodes.

I used to have a crapload, but now I'm sure my wallet is like 200k, anyways, could probably put half that into someone willing to revive this coin.

203.20.114.252 is up again, and I can see a new peer starting from height 0... Smiley

I'm up to 240,000+ blocks.

Did you ever get fully synced?
legendary
Activity: 2268
Merit: 1092
Any chance you have the blockchain still? Maybe put it onto the network, I've added the nodes.

I used to have a crapload, but now I'm sure my wallet is like 200k, anyways, could probably put half that into someone willing to revive this coin.

203.20.114.252 is up again, and I can see a new peer starting from height 0... Smiley
full member
Activity: 243
Merit: 100
getblockhash 373223
d4a64d99aca67705edb2755a6f0470fffb40e4c005dba72079f1916b46dbe343

[...]

15:56:12
getblockhash 373223
15:56:12
d4a64d99aca67705edb2755a6f0470fffb40e4c005dba72079f1916b46dbe343

Right, so now we've established that my database is identical to yours, up to the height I was synced at (373223). And it looks like you've connected to me, I'm now at height 410490, but you dropped off before it fully synced. What happened?

203.20.114.252 is a dedicated 24/7/365 server with a static IP, so with such a tiny network (currently) it would make sense to get this node fully synced.

Any chance you have the blockchain still? Maybe put it onto the network, I've added the nodes.

I used to have a crapload, but now I'm sure my wallet is like 200k, anyways, could probably put half that into someone willing to revive this coin.

legendary
Activity: 2268
Merit: 1092
getblockhash 373223
d4a64d99aca67705edb2755a6f0470fffb40e4c005dba72079f1916b46dbe343

[...]

15:56:12
getblockhash 373223
15:56:12
d4a64d99aca67705edb2755a6f0470fffb40e4c005dba72079f1916b46dbe343

Right, so now we've established that my database is identical to yours, up to the height I was synced at (373223). And it looks like you've connected to me, I'm now at height 410490, but you dropped off before it fully synced. What happened?

203.20.114.252 is a dedicated 24/7/365 server with a static IP, so with such a tiny network (currently) it would make sense to get this node fully synced.
legendary
Activity: 2268
Merit: 1092
getblockhash 373223
d4a64d99aca67705edb2755a6f0470fffb40e4c005dba72079f1916b46dbe343

getblockhash 300000
159c1abd78d6a84a12bf9088ce5aa942fe1ba248300045da87befc36475af9c3

getblockhash 200000
a6666806aff80882e26d752c5d7f3f952ce1e88e69aa0bb13802354d5b2a5663


print screen https://yadi.sk/i/ENmAXq6ovqYBW

all files
https://yadi.sk/d/d-KmsIyQvqYT5


Yeah, so what makes you think that 203.20.114.252 is not running a valid client? Check the block hashes above in your wallet's RPC console, see if they match...
member
Activity: 68
Merit: 18
getblockhash 373223
d4a64d99aca67705edb2755a6f0470fffb40e4c005dba72079f1916b46dbe343

getblockhash 300000
159c1abd78d6a84a12bf9088ce5aa942fe1ba248300045da87befc36475af9c3

getblockhash 200000
a6666806aff80882e26d752c5d7f3f952ce1e88e69aa0bb13802354d5b2a5663


print screen https://yadi.sk/i/ENmAXq6ovqYBW

all files
https://yadi.sk/d/d-KmsIyQvqYT5
legendary
Activity: 2268
Merit: 1092
getblockhash 373223
d4a64d99aca67705edb2755a6f0470fffb40e4c005dba72079f1916b46dbe343

getblockhash 300000
159c1abd78d6a84a12bf9088ce5aa942fe1ba248300045da87befc36475af9c3

getblockhash 200000
a6666806aff80882e26d752c5d7f3f952ce1e88e69aa0bb13802354d5b2a5663
legendary
Activity: 2268
Merit: 1092
addnode=203.20.114.252 not correct.   not bells

Eh? Well I have something called bellsd running on that IP, news to me!

Code:
coins    bellsd     18679 6  tcp4   203.20.114.252:19919  *:*
coins    bellsd     18679 14 tcp4   203.20.114.252:19919  45.50.28.121:57163

edit: the bellsd source I have has a genesis block hash of 0xe5be24df57c43a82d15c2f06bda961296948f8f8eb48501bed1efb929afe0698 which matches main.cpp on your github clone. Have we gone off on two different blockchain forks, perhaps?
member
Activity: 68
Merit: 18
I did not restart my BEL wallet after my last reboot. I'll start it up again.
45.50.28.121 still

I connected to 203.20.114.252 yea! we might just be live again

I've synced to you (height 370974) but the last block was minted nearly a year ago. How long has your wallet been off? If you dropped out but others kept mining past that point, neither of us will have the full chain, and any mining by either of us will create a fork.

Hey everyone, fire up your old wallets so we can properly agree on the correct blockchain. Cheesy

addnode=203.20.114.252

 last block 429222
data base https://www.dropbox.com/s/ifg342ps3qrwqsy/bells.rar?dl=0             My base is not enough to complete ~5 days.  who has a complete database? lacks ~5 days until when he died bells
mirror https://yadi.sk/d/yhOwgHFHvqcnk
Byron must have a full database. But I think he's lost it.

client https://www.dropbox.com/s/yfcrhgzbabhv3zt/Bells-0.8.7.1.zip?dl=0
mirror   https://yadi.sk/d/7vjzNv-AvqcgL         I saved the last original,

source https://github.com/bells-coin/bells-coin.git                                         I made a clone. Old someone deleted.

addnode=203.20.114.252 not correct.   not bells
domain name bellscoin.org   i lost. I wanted to resurrect bells. but I was busy. a lot of work
legendary
Activity: 2268
Merit: 1092
I did not restart my BEL wallet after my last reboot. I'll start it up again.
45.50.28.121 still

I connected to 203.20.114.252 yea! we might just be live again

I've synced to you (height 370974) but the last block was minted nearly a year ago. How long has your wallet been off? If you dropped out but others kept mining past that point, neither of us will have the full chain, and any mining by either of us will create a fork.

Hey everyone, fire up your old wallets so we can properly agree on the correct blockchain. Cheesy

addnode=203.20.114.252
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
I did not restart my BEL wallet after my last reboot. I'll start it up again.
45.50.28.121 still

I connected to 203.20.114.252 yea! we might just be live again
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
I did not restart my BEL wallet after my last reboot. I'll start it up again.
legendary
Activity: 2268
Merit: 1092
Try connecting to 203.20.114.252

I've found one other peer, but it has a completely different version and block count, so I suspect it's not a BEL client.

Pulled 950 historical peer IPs out of my logs, so the client is trying them all now.

addnode=203.20.114.252
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
What is your nodes address? Maybe I can connect to you.
I do not have a real Ip address
addnode=45.50.28.121:19919  not working. port closed

odd i checked my .conf file for port 19919  rcp port 19920
firewall has the bells qt exe open

none of my other wallets have issues. i'll check comodo sandbox is off later tonight
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
45.50.28.121 is my node

have no peers no nodes connected but show networkhashps" : 2306015
so where are they from?
no connect

port?


19919
no connect
 Sad

What is your nodes address? Maybe I can connect to you.
member
Activity: 68
Merit: 18
45.50.28.121 is my node

have no peers no nodes connected but show networkhashps" : 2306015
so where are they from?
no connect

port?


19919
no connect
 Sad
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
45.50.28.121 is my node

have no peers no nodes connected but show networkhashps" : 2306015
so where are they from?
no connect

port?


19919
member
Activity: 68
Merit: 18
45.50.28.121 is my node

have no peers no nodes connected but show networkhashps" : 2306015
so where are they from?
no connect

port?
Pages:
Jump to: