Bitcoin Forum

Not a bad plan. I am surprised more coins don't do this.

That's cause they're not 51% proof; this coin has a different concept.

More no. of nodes means less chance of the bad blockchain syncing.

and there is the rub. You're not 51% proof, you're just hoping that no one ever sees a malicious mode. In fact, I'd say this is even easier to fork than a standard PoW coin, because all you have to do is mint 3 or 4 blocks ahead, and your coin will fork itself off, and then it's just a matter of getting nodes to see the malicious nodes before your legit nodes (ie, easily done with a DDoS).

Posting your IP address here is dangerous in itself of course as well. Let's hope there is no security flaw in your wallet cause otherwise you're painting a huge target on people.

Refusing to accept a superior blockchain is not "51% proof", it just means that when a node gets forked off, it will never recover by itself, leading to even more dangerous actions happening, such as if hash power leaves the chain (and then it becomes even easier to 51% the old chain).

Also, before you ask, your 51% "bounty" would not cover my time.. up it to something more lucrative, and maybe I'll prove it ;)

because all you have to do is mint 3 or 4 blocks ahead

easily done with a DDoS

Refusing to accept a superior blockchain is not "51% proof"

when a node gets forked off

The situation when long forks are desirable is when there's a coincidence of multiple genuine conflicting miners (considering non-restricting networks). The probability of the coincidence is very low and reduces dramatically as each block gets added in either of the forked chain. By the time 12 blocks have been mined on the forks, the probability has reduced to a practically impossible value. Had this not been true, a 51% attack would've been a coincidence. Till date, off all cryptocurreny history and the billions of blocks mined, this coincidence has never happened. A 51% attack requires skills, it can't be done by chance.

There is only one configuration in which long forks are genuinely made - when the miners produce forked blocks at the same height. If some miner has made a block at, say the 3rd or 4th last block (or lower than that), then it points to either 1 or 2.

Let's take an e.g. of a set of miners A and B. Suppose A mines a new block (named 100A, where 100 is depth and A is the miner's name), but before the block reaches B, B generates a new block (100B). In this situation a fork is made. B continues to mine on on 100B and A continues to mine on 100A. Let's take the probability of this happening -

(probability of B mining block 100B (depends on hash rate) at time t)*(probability of A mining block 100A (depends on hash rate) at time t+D)

Where D is the delta; D is a unit of time which is less than the time it takes for a block to traverse; that's why B found a new block and broadcasted it to the network without marking it stale.

A high hash rate and low difficulty will increase the probability of of a forked block. This is where eDRv2 kicks in and makes this situation less likely than normal.

There is low (but not impossible) probability of this situation.

 For this fork to continue, B should generate a new block 101B, and A should generate a block 101A before each of the blocks reach the other set of miners. So the the probability involved here is -
 
(probability of B mining block 100B (depends on hash rate) at time t)*(probability of A mining block 100A (depends on hash rate) at time t+D)*(probability of B mining block 101B (depends on hash rate) at time T)*(probability of A mining block 101A (depends on hash rate) at time T+D)

So this is exponentially unlikely to happen and we're still at just the 2nd block of the parallel forks.

The game changer difference between this and the 100A/B situation is the difficulty of 101A/B. For A to continue mining on 101A and for B to continue mining on 101B, the difficulty of both these blocks must be identical; that means blocks 100A/B must have identical timestamps. So d has to be less than a second; otherwise one of 101A/B will be selected as the main chain.

All this has to happen for each block till block 12 (or 6, depending on the coin); so a 51% attack by coincidence is impossible to happen; and we've seen this happening.

if hash power leaves the chain (and then it becomes even easier to 51% the old chain).

Regardless of how powerful the attacker is once a transaction is confirmed (12 blocks), you cannot reverse it.

Also, before you ask, your 51% "bounty" would not cover my time.. up it to something more lucrative, and maybe I'll prove it Wink

46.238.44.222 , I'm in...

23.102.34.115 , wallet is open

Just in now ... 58.26.196.129
que...

106.8.72.122   

and  please give me  some nodes ~~

46.238.44.222 , I'm in...

And what exactly stops people from running hundreds of wallets across VMs and increase the inflation of the coin so much that's it's utterly worthless?

14 hours. Your BIGcoin address to get 1176 HUGE...

Interesting... before I download the wallet, may I know the current price of Huge ?

14 hours. Your BIGcoin address to get 1176 HUGE...

sent you a PM..

maybe you can find you answer in this exchange

https://www.bynergy.com/market/HFC/OTC

i don't want to open and see the price

Yeah, send you the reward.

Other please wait...

You don't appear to have a stable Internet connection.

It connects, disconnects.

PM me the contents of your debug.log.

127.0.0.1 - I'm In!

109.87.255.75
BqPefaXyNPeZGYqe391H9HQu5sesv1C7tf

i'm in

I left you a PM.

Bk72ZebkHj74x234W1eW71t82Ms7b1c2Gb

Posting your IP address here is dangerous in itself of course as well. Let's hope there is no security flaw in your wallet cause otherwise you're painting a huge target on people.

Or just as a all round bad idea. Associating your personal nick with an IP on THESE forums is asking for a metric shit ton of trouble.

2015-01-31,08:39:50 (UTC).

23.102.34.115 , wallet is open

Network Ip : 192.168.0.108

BmMfaL33yAnX9U5PHDjjiQu4HgSwG8TXJQ

146.148.66.100

i'm in :D

Bmzw5DPqqg4wgL47RR69eV2Q3EeSyJ5jhz

347. You're still connected.

2655 HUGE.

Still connected.

thank you still connect   ;D

46.238.44.222 , I'm in...

What about me ... 46.238.44.222 :)

You're now disconnected.

146.148.66.100

i'm in :D

Bmzw5DPqqg4wgL47RR69eV2Q3EeSyJ5jhz

107.167.185.96 Im in :)

BWp2HD9qBZ4AwBGmBwQABKktZKCJ7obfmy

60db5d734ba5c9359bd94b5e35af96cdabc372f630dd1d77645c6cfde821c77e

386.66

Thanks for the post. I will definitely download the wallet and post here...a quick question before that. What is the current value ? I couldn't find any data here https://www.bynergy.com/market/HFC/OTC

Thanks

Sorry to repeat my question but I was waiting for an answer.
Thanks

It was 15 min maintenance...
Edit: I forgot that I changed the ip:     78.83.53.78

You're now disconnected.

0289f80d1272398e18faaae06154c4425f0f0ccbc7bd673ee15a1906aa7215db

804.95

Apart from the previous one.

I had elecricity down , and now wallet cant sync..
EDIT: changed the PC an IP: 89.190.195.82

Cant sync , allways crashing with error that cant load tha database with wallet.dat ( error -30974). It apears on win7 and 8.1 both...

my ip address is dynamic
change every reconnect the internet
can do this sir ?

There are too many transactions in the wallet. You must have mined quite a lot.

Backup the wallet.dat, and remove it. And then restart.

If you want to use your previous balance (in the backup wallet.dat), sync completely and after shutting down the wallet restore your old wallet.dat. You'll be able to use the balance.

I have only 3 transactions on wallet , but still cant open it. When I resync base with new wallet , shutdown wallet and restore the main one its the same error that cant connect the wallet with database :

https://i.imgur.com/uo5JdGa.jpg

elecricity down

I syncronized again, restore the wallet. First I tried starting it with salvagwallet , the result is:

https://i.imgur.com/eiR6w06.jpg

Then I tried with pywallet, same error...

Edit: Finally succeed to sync , now its OK
EDIT2: IP - 89.190.195.82

OPs is this offer still running ?
because i am not hear any news from you since im posting my IP address
my wallet still running and need confirmation from you, i am connected or not :)

Would you share some nodes ?
EDIT: I fixed everything , IP: 89.190.195.82

Would you share some nodes ?
EDIT: I fixed everything , IP: 89.190.195.82

Not sure if this is the right thread or if I am missing another.

Last night was a great night for solo mining.  Is there a pool for this coin?  And if there is did it go down?  Not that I am complaining but I mined 10x more coins in one night than 3 days previous.

Also is there a reason it takes so long for mined coins to become available?  Thanks

If you want to benefit from BIGcoin, you should start mining early. The network gives no incentives to opportunistic miners or multipools.

That's because it take around 48 hours for your mined coins to get confirmed; so no more dumping at a pump.

more than one day without any incomes ?

Yes, paid just in.

28fd05d6b2fa52c32b067f9a416bc3639bac1e8ab22ac6a93a81989ae5307ec8

Sign in
My IP : 36.84.227.224
Addy : BfbbC5szn4YP8SWSG3hLQuNPrTHLNZeGum
Am i connected ?

128.199.32.122

BYD4X1r1kkNwQK9bT9A7dRcVroonhLDhyU

ip add : 192.99.70.65
bigcoin : Bdst7Eh7QoiCVG8JGwC46F36xvGb4zoZMX

You were.

128.199.32.122

BYD4X1r1kkNwQK9bT9A7dRcVroonhLDhyU

My Wallet open since  : Sun Feb 8 13:57:24 2015

That's 21:21:13 UTC

The payment cant be done until you disconnect. Otherwise how do we figure out your uptime?

My pc uptime is 1 month since last reboot

wallet will remain online until i turn off

should i turn off my wallet to got payment ?

and

reward will cointinue count until im disconnected or got a limited time ?

The count will continue until you're disconnect.

I give the rewards in every 2 days.

Actually I got a big responsibility of testing the wallets and designing/thinking up on new concepts and protocol mods. So I got very limited time.