Closed Thread

[TwinWinNerD]

I've noticed there is dust for every password so you could conceivably make some cash scooping it all up. Of course you might stumble onto someones account doing that as well. Does the account lock to your IP when you create it?

There is not dust in every account, I just stumbled onto an obvious password.

That password? "password123" 

Pretty much.

I do have some concern about the entropy of the account generator.  I hope collision is not too easy to generate, heh.

The problem is that people will make rainbow tables and get your password by bruteforcing the shit out of it. Would move asap!

[patmast3r]

I've noticed there is dust for every password so you could conceivably make some cash scooping it all up. Of course you might stumble onto someones account doing that as well. Does the account lock to your IP when you create it?

There is not dust in every account, I just stumbled onto an obvious password.

That password? "password123" 

Pretty much.

I do have some concern about the entropy of the account generator.  I hope collision is not too easy to generate, heh.

The problem is that people will make rainbow tables and get your password by bruteforcing the shit out of it. Would move asap!

I'm sure people are already bruting the crap out of it. Simply sending a POST and checking the resulting json for balance. I'm sure we'll read about some stolen NODE soon enough

[TwinWinNerD]

I've noticed there is dust for every password so you could conceivably make some cash scooping it all up. Of course you might stumble onto someones account doing that as well. Does the account lock to your IP when you create it?

There is not dust in every account, I just stumbled onto an obvious password.

That password? "password123" 

Pretty much.

I do have some concern about the entropy of the account generator.  I hope collision is not too easy to generate, heh.

The problem is that people will make rainbow tables and get your password by bruteforcing the shit out of it. Would move asap!

I'm sure people are already bruting the crap out of it. Simply sending a POST and checking the resulting json for balance. I'm sure we'll read about some stolen NODE soon enough

Yes, happend to brainwallet, to NXT, to NAS, to everyother brainwallet coin and it will happen to NODE.

[HunterMinerCrafter]

Exploring this coin's data has been very interesting.  Here is the top of the richlist:

Code:

[ { acct: '15007997926042764084', amt: 213033004.95773 },
  { acct: '14302536936654097014', amt: 150000000 },
  { acct: '17982531019448340817', amt: 50000000 },
  { acct: '3216421205779526334', amt: 50000000 },
  { acct: '4768052738330486459', amt: 50000000 },
  { acct: '17629803831991308677', amt: 40000000 },
  { acct: '1092564458935116408', amt: 24895434.14929 },
  { acct: '2070531393911881683', amt: 20961290 },
  { acct: '1797803473310418787', amt: 20000000 },
  { acct: '14367295516694207452', amt: 17866819.99999 },
  { acct: '2322235302182984849', amt: 15572244 },
  { acct: '15570446243067519439', amt: 15571244 },
  { acct: '17591617551191551229', amt: 10000017.942 },
  { acct: '7646129982963216265', amt: 6587834 },
  { acct: '15442941950336314161', amt: 5988939.98 },
  { acct: '10363598084526802812', amt: 5967940 },
  { acct: '149545601043747358', amt: 5101074.54588 },
  { acct: '5592344497652814264', amt: 4192258 },
  { acct: '7488774142909981577', amt: 4192258 },
  { acct: '14927530973246814016', amt: 4192249.99999 },
  { acct: '2083327399302860846', amt: 3594364 },
  { acct: '14898219332053103255', amt: 3593364 },
  { acct: '14854211854869071145', amt: 3593364 },
  { acct: '11784916107927768102', amt: 3593364 },
  { acct: '6544492203374965037', amt: 3015469.99998 },
  { acct: '13974667736699431314', amt: 2744469.99999 },
  { acct: '11227004137347710224', amt: 2395576 },
  { acct: '4872651434939660095', amt: 2395576 },
  { acct: '9024536475366138999', amt: 2395576 },
  { acct: '12225342230230813959', amt: 1796682 },
  { acct: '8084728589437427069', amt: 1796682 },
  { acct: '1709936176935780779', amt: 1796682 },
  { acct: '9806413029992456055', amt: 1796682 },
  { acct: '3186187453749542557', amt: 1796682 },
  { acct: '16205043044276658881', amt: 1796682 },
  { acct: '2030099868381150815', amt: 1198588.3035 },
  { acct: '94741177007855643', amt: 1197788 },
  { acct: '5082548281909971876', amt: 1197788 },
  { acct: '2829299209564554264', amt: 1197788 },
  { acct: '16292443660919351336', amt: 1197788 },
  { acct: '3155722020360433425', amt: 1197788 },
  { acct: '16110121636695746144', amt: 1197788 },
  { acct: '14086637287909711020', amt: 1197788 },
  { acct: '14654469534200754721', amt: 1197788 },
  { acct: '16570391779901095218', amt: 1197788 },
  { acct: '8194832948072259390', amt: 1197788 },
  { acct: '8995298798558043073', amt: 1197788 },
  { acct: '12122996885260074146', amt: 1197788 },
  { acct: '321670142463671049', amt: 1197788 },
  { acct: '5619082415367514029', amt: 1197788 },
  { acct: '9359354781415431877', amt: 1197788 },
  { acct: '16619749170240298664', amt: 1197788 },
  { acct: '12320163121948644447', amt: 654325.35906 },
  { acct: '17544135771292067152', amt: 598895 },
  { acct: '864063906128527339', amt: 598894 },
  { acct: '11382852887963396761', amt: 598894 },
  { acct: '2344479021672616820', amt: 598894 },

The rest are all 598894 until we get to the bottom of the list, which is much more interesting!

Code:

  { acct: '14326427415077807235', amt: 598894 },
  { acct: '15794062422179730423', amt: 598894 },
  { acct: '18317896172425583208', amt: 598893.99997 },
  { acct: '18239362792954542021', amt: 598886 },
  { acct: '14772281011108709717', amt: 596794 },
  { acct: '4046257829189253934', amt: 250000 },
  { acct: '14052525185349154731', amt: 100000 },
  { acct: '16711743091738550527', amt: 26084.68901 },
  { acct: '1057166529672831789', amt: 2099.99999 },
  { acct: '149545601043747359', amt: 302 },
  { acct: '149545601043747350', amt: 120 },
  { acct: '2318039537359438386', amt: 35 },
  { acct: '10540349027233847435', amt: 16 },
  { acct: '5511243549068604629', amt: 8 },
  { acct: '8993283969480711038', amt: 7.99997 },
  { acct: '18098809587477536662', amt: 4.99999 },
  { acct: '2807154910500019257', amt: 2 },
  { acct: '14777837390141087036', amt: 2 },
  { acct: '16519258667626161765', amt: 1 },
  { acct: '141811809624302464', amt: 1 },
  { acct: '6618192569618682016', amt: 1 },
  { acct: '3863393017664103565', amt: 0.99999 },
  { acct: '17689260977368600948', amt: 0.99999 },
  { acct: '5921881255187408995', amt: 0.99999 },
  { acct: '16711743091738550526', amt: 0.56 },
  { acct: '5412190510193552950', amt: 0.09218 },
  { acct: '18147114505253343836', amt: 0.01994 },
  { acct: '15452014960459345794', amt: 0 },
  { acct: '14980718954024111172', amt: 0 },
  { acct: '7520636997306874572', amt: -0.00001 },
  { acct: '18417060698680254365', amt: -0.00001 },
  { acct: '6943953658916908917', amt: -0.00001 },
  { acct: '14931191424261653564', amt: -5.07338 },
  { acct: '7684489094182123925', amt: -1000000000 } 

It seems someone did find a way to make nodecoin appear magically, but it was earlier than I thought.  There were just over 5 extra NODE in existence for awhile.  They appear to have since been "destroyed" as the ledger currently balances to precisely the expected coin cap, less the 143.47498 NODE eaten up in fees. (EDIT: NM the 5 extra coins are still out there somewhere.  NodeCoin is over supply!)  The person who did this (it is quite a "visible" event in the tx data) also appears to almost certainly control at least one of the top addresses from the rich list.

[koop4u]

Exploring this coin's data has been very interesting.  Here is the top of the richlist:

Code:

[ { acct: '15007997926042764084', amt: 213033004.95773 },
  { acct: '14302536936654097014', amt: 150000000 },
  { acct: '17982531019448340817', amt: 50000000 },
  { acct: '3216421205779526334', amt: 50000000 },
  { acct: '4768052738330486459', amt: 50000000 },
  { acct: '17629803831991308677', amt: 40000000 },
  { acct: '1092564458935116408', amt: 24895434.14929 },
  { acct: '2070531393911881683', amt: 20961290 },
  { acct: '1797803473310418787', amt: 20000000 },
  { acct: '14367295516694207452', amt: 17866819.99999 },
  { acct: '2322235302182984849', amt: 15572244 },
  { acct: '15570446243067519439', amt: 15571244 },
  { acct: '17591617551191551229', amt: 10000017.942 },
  { acct: '7646129982963216265', amt: 6587834 },
  { acct: '15442941950336314161', amt: 5988939.98 },
  { acct: '10363598084526802812', amt: 5967940 },
  { acct: '149545601043747358', amt: 5101074.54588 },
  { acct: '5592344497652814264', amt: 4192258 },
  { acct: '7488774142909981577', amt: 4192258 },
  { acct: '14927530973246814016', amt: 4192249.99999 },
  { acct: '2083327399302860846', amt: 3594364 },
  { acct: '14898219332053103255', amt: 3593364 },
  { acct: '14854211854869071145', amt: 3593364 },
  { acct: '11784916107927768102', amt: 3593364 },
  { acct: '6544492203374965037', amt: 3015469.99998 },
  { acct: '13974667736699431314', amt: 2744469.99999 },
  { acct: '11227004137347710224', amt: 2395576 },
  { acct: '4872651434939660095', amt: 2395576 },
  { acct: '9024536475366138999', amt: 2395576 },
  { acct: '12225342230230813959', amt: 1796682 },
  { acct: '8084728589437427069', amt: 1796682 },
  { acct: '1709936176935780779', amt: 1796682 },
  { acct: '9806413029992456055', amt: 1796682 },
  { acct: '3186187453749542557', amt: 1796682 },
  { acct: '16205043044276658881', amt: 1796682 },
  { acct: '2030099868381150815', amt: 1198588.3035 },
  { acct: '94741177007855643', amt: 1197788 },
  { acct: '5082548281909971876', amt: 1197788 },
  { acct: '2829299209564554264', amt: 1197788 },
  { acct: '16292443660919351336', amt: 1197788 },
  { acct: '3155722020360433425', amt: 1197788 },
  { acct: '16110121636695746144', amt: 1197788 },
  { acct: '14086637287909711020', amt: 1197788 },
  { acct: '14654469534200754721', amt: 1197788 },
  { acct: '16570391779901095218', amt: 1197788 },
  { acct: '8194832948072259390', amt: 1197788 },
  { acct: '8995298798558043073', amt: 1197788 },
  { acct: '12122996885260074146', amt: 1197788 },
  { acct: '321670142463671049', amt: 1197788 },
  { acct: '5619082415367514029', amt: 1197788 },
  { acct: '9359354781415431877', amt: 1197788 },
  { acct: '16619749170240298664', amt: 1197788 },
  { acct: '12320163121948644447', amt: 654325.35906 },
  { acct: '17544135771292067152', amt: 598895 },
  { acct: '864063906128527339', amt: 598894 },
  { acct: '11382852887963396761', amt: 598894 },
  { acct: '2344479021672616820', amt: 598894 },

The rest are all 598894 until we get to the bottom of the list, which is much more interesting!

Code:

  { acct: '14326427415077807235', amt: 598894 },
  { acct: '15794062422179730423', amt: 598894 },
  { acct: '18317896172425583208', amt: 598893.99997 },
  { acct: '18239362792954542021', amt: 598886 },
  { acct: '14772281011108709717', amt: 596794 },
  { acct: '4046257829189253934', amt: 250000 },
  { acct: '14052525185349154731', amt: 100000 },
  { acct: '16711743091738550527', amt: 26084.68901 },
  { acct: '1057166529672831789', amt: 2099.99999 },
  { acct: '149545601043747359', amt: 302 },
  { acct: '149545601043747350', amt: 120 },
  { acct: '2318039537359438386', amt: 35 },
  { acct: '10540349027233847435', amt: 16 },
  { acct: '5511243549068604629', amt: 8 },
  { acct: '8993283969480711038', amt: 7.99997 },
  { acct: '18098809587477536662', amt: 4.99999 },
  { acct: '2807154910500019257', amt: 2 },
  { acct: '14777837390141087036', amt: 2 },
  { acct: '16519258667626161765', amt: 1 },
  { acct: '141811809624302464', amt: 1 },
  { acct: '6618192569618682016', amt: 1 },
  { acct: '3863393017664103565', amt: 0.99999 },
  { acct: '17689260977368600948', amt: 0.99999 },
  { acct: '5921881255187408995', amt: 0.99999 },
  { acct: '16711743091738550526', amt: 0.56 },
  { acct: '5412190510193552950', amt: 0.09218 },
  { acct: '18147114505253343836', amt: 0.01994 },
  { acct: '15452014960459345794', amt: 0 },
  { acct: '14980718954024111172', amt: 0 },
  { acct: '7520636997306874572', amt: -0.00001 },
  { acct: '18417060698680254365', amt: -0.00001 },
  { acct: '6943953658916908917', amt: -0.00001 },
  { acct: '14931191424261653564', amt: -5.07338 },
  { acct: '7684489094182123925', amt: -1000000000 } 

It seems someone did find a way to make nodecoin appear magically, but it was earlier than I thought.  There were just over 5 extra NODE in existence for awhile.  They appear to have since been "destroyed" as the ledger currently balances to precisely the expected coin cap, less the 143.47498 NODE eaten up in fees.  The person who did this (it is quite a "visible" event in the tx data) also appears to almost certainly control at least one of the top addresses from the rich list.

Nicely done!

Yep Skill has access to all the Top accounts! Those are the 40% of total coins divided to Particular Funds

https://docs.google.com/spreadsheet/ccc?key=0AnYj5G7gBeXIdGtHam1UOXlDaDR6VFFZMGp3bVRnSHc&usp=drive_web#gid=4

[HunterMinerCrafter]

Nicely done!

Yep Skill has access to all the Top accounts! Those are the 40% of total coins divided to Particular Funds

https://docs.google.com/spreadsheet/ccc?key=0AnYj5G7gBeXIdGtHam1UOXlDaDR6VFFZMGp3bVRnSHc&usp=drive_web#gid=4

So the 25million coin account that pulled off a negative balance in the early blocks is a dev?  Can he destroy the extra coins, and then fix the implementation so that extra coins can't exist? XD

I'm a little concerned about a crypto-currency where this could happen at all.  How exactly is a chain supposed to deal with negative fees in its history, or more coins than is possible?  Seems a little scary...

Currently you can also still send transactions with no fees that appear to have fees, creating a tx where the amount+fees is more than your balance.  I'm assuming these fee coins (that don't actually exist) are going somewhere (??!?!) so this would basically mean I created new coins above the cap today, too.  Sorry about that - but at least they went into devs' hands, presumably.

I hope there are not more critical bugs.  I'd really like to see a javascript coin, but not if it is just simply broken like this.  So many bugs, and this is before we've even seen source!

I'm glad that I only became a stakeholder by accident! 

[SillkRoad]

Nicely done!

Yep Skill has access to all the Top accounts! Those are the 40% of total coins divided to Particular Funds

https://docs.google.com/spreadsheet/ccc?key=0AnYj5G7gBeXIdGtHam1UOXlDaDR6VFFZMGp3bVRnSHc&usp=drive_web#gid=4

So the 25million coin account that pulled off a negative balance in the early blocks is a dev?  Can he destroy the extra coins, and then fix the implementation so that extra coins can't exist? XD

I'm a little concerned about a crypto-currency where this could happen at all.  How exactly is a chain supposed to deal with negative fees in its history, or more coins than is possible?  Seems a little scary...

Currently you can also still send transactions with no fees that appear to have fees, creating a tx where the amount+fees is more than your balance.  I'm assuming these fee coins (that don't actually exist) are going somewhere (??!?!) so this would basically mean I created new coins above the cap today, too.  Sorry about that - but at least they went into devs' hands, presumably.

I hope there are not more critical bugs.  I'd really like to see a javascript coin, but not if it is just simply broken like this.  So many bugs, and this is before we've even seen source!

I'm glad that I only became a stakeholder by accident!  

What additional coins?
All coins in general give 1 billion
What comes from one account to another, it would test

negative balance does not happen

First you mess commission for distribution of coins commission has been disabled to 0.00001
By default it is 0.35%

Thanks for testing and error, but we have just compared our data and we do not leave a negative balance

[HunterMinerCrafter]

What additional coins?
All coins in general give 1 billion
What comes from one account to another, it would test

negative balance does not happen

Here are the first 35 blocks.  Perhaps there's a bug in my code?  I might have some rounding error to explain the -0.00001 accounts, but the -5 account is very distinct.

The transaction lines go block #, sender, receiver, amount, fee with the corresponding balance adjustments below each.

Code:

BLOCK 0
0 'ASNy9ZgzuLfc8qd0' '7684489094182123925' '1797803473310418787' 20000000 0
- 7684489094182123925 from 0 to -20000000
+ 1797803473310418787 from 0 to 20000000

0 'd1gjdPyuDEX9gJ8b' '7684489094182123925' '4768052738330486459' 50000000 0
- 7684489094182123925 from -20000000 to -70000000
+ 4768052738330486459 from 0 to 50000000

0 'Spz1mJ70qJLb6SQs' '7684489094182123925' '15007997926042764084' 600000000 0
- 7684489094182123925 from -70000000 to -670000000
+ 15007997926042764084 from 0 to 600000000

0 'A3lQipFw05IsY7bt' '7684489094182123925' '1092564458935116408' 30000000 0
- 7684489094182123925 from -670000000 to -700000000
+ 1092564458935116408 from 0 to 30000000

0 'fDxyGEnuleibBUfN' '7684489094182123925' '3216421205779526334' 50000000 0
- 7684489094182123925 from -700000000 to -750000000
+ 3216421205779526334 from 0 to 50000000

0 'MbHLGBKFU76zijGV' '7684489094182123925' '17629803831991308677' 40000000 0
- 7684489094182123925 from -750000000 to -790000000
+ 17629803831991308677 from 0 to 40000000

0 '0O7ajR5ruiNSFPDj' '7684489094182123925' '17982531019448340817' 50000000 0
- 7684489094182123925 from -790000000 to -840000000
+ 17982531019448340817 from 0 to 50000000

0 'tdduipUESCcxX6tP' '7684489094182123925' '14302536936654097014' 150000000 0
- 7684489094182123925 from -840000000 to -990000000
+ 14302536936654097014 from 0 to 150000000

0 '8gdDjACvwIK6eNFC' '7684489094182123925' '17591617551191551229' 10000000 0
- 7684489094182123925 from -990000000 to -1000000000
+ 17591617551191551229 from 0 to 10000000

BLOCK 1
1 'fFGl48vJpEtNLbqp' '17591617551191551229' '14931191424261653564' 0.15 0
- 17591617551191551229 from 10000000 to 9999999.85
+ 14931191424261653564 from 0 to 0.15

BLOCK 2
2 'JdU3cajGt9U1DcHt' '17591617551191551229' '14931191424261653564' 10.15 0
- 17591617551191551229 from 9999999.85 to 9999989.7
+ 14931191424261653564 from 0.15 to 10.3

BLOCK 3
3 '1OjNLoUj03SUGnzz' '14931191424261653564' '17591617551191551229' 0.01 1
- 14931191424261653564 from 10.3 to 9.29
+ 17591617551191551229 from 9999989.7 to 9999989.71

BLOCK 4
4 'mVdEWubbFL6HEEGt' '17591617551191551229' '14931191424261653564' 0.02 1
- 17591617551191551229 from 9999989.71 to 9999988.69
+ 14931191424261653564 from 9.29 to 9.31

4 '3OndkBi19qyD8X29' '17591617551191551229' '14931191424261653564' 0.02 1
- 17591617551191551229 from 9999988.69 to 9999987.67
+ 14931191424261653564 from 9.31 to 9.33

4 'bdfhAjYRBd8ozcX5' '17591617551191551229' '14931191424261653564' 0.02 1
- 17591617551191551229 from 9999987.67 to 9999986.65
+ 14931191424261653564 from 9.33 to 9.35

BLOCK 5
5 'WT3UpaiU9LemIZxu' '1092564458935116408' '14777837390141087036' 2 1
- 1092564458935116408 from 30000000 to 29999997
+ 14777837390141087036 from 0 to 2

BLOCK 6
6 'lFBebXQFLB8cxc1S' '1092564458935116408' '141811809624302464' 1 1
- 1092564458935116408 from 29999997 to 29999995
+ 141811809624302464 from 0 to 1

BLOCK 7
7 'SgpLSNGI8tEvByBX' '1092564458935116408' '16711743091738550527' 10.00257 1
- 1092564458935116408 from 29999995 to 29999983.99743
+ 16711743091738550527 from 0 to 10.00257

BLOCK 8
8 '08pnwlwALhd7FKnF' '1092564458935116408' '16711743091738550527' 50 1
- 1092564458935116408 from 29999983.99743 to 29999932.99743
+ 16711743091738550527 from 10.00257 to 60.00257

BLOCK 9
9 'kpWfqh5sgDJk58mE' '1092564458935116408' '16711743091738550527' 5 3
- 1092564458935116408 from 29999932.99743 to 29999924.99743
+ 16711743091738550527 from 60.00257 to 65.00257

BLOCK 10
10 '8pbssmgRPJ2dCGka' '16711743091738550527' '12320163121948644447' 33.36656 1
- 16711743091738550527 from 65.00257 to 30.63601
+ 12320163121948644447 from 0 to 33.36656

BLOCK 11
11 'Ck27HiosQlVWqhxh' '16711743091738550527' '10540349027233847435' 1 1
- 16711743091738550527 from 30.63601 to 28.63601
+ 10540349027233847435 from 0 to 1

BLOCK 12
12 'yjZXXBAVjxfsLdjL' '16711743091738550527' '10540349027233847435' 10 1
- 16711743091738550527 from 28.63601 to 17.63601
+ 10540349027233847435 from 1 to 11

BLOCK 13
13 'K1gfz3BfOOGZgNDl' '16711743091738550527' '10540349027233847435' 5 1
- 16711743091738550527 from 17.63601 to 11.63601
+ 10540349027233847435 from 11 to 16

BLOCK 14
14 'W4uUVFwUKWPviBpm' '1092564458935116408' '149545601043747358' 100000 1
- 1092564458935116408 from 29999924.99743 to 29899923.99743
+ 149545601043747358 from 0 to 100000

BLOCK 15
15 '8e7ILQjKpXZUiLhg' '1092564458935116408' '149545601043747358' 3500000 1
- 1092564458935116408 from 29899923.99743 to 26399922.99743
+ 149545601043747358 from 100000 to 3600000

BLOCK 16
16 'Yoju80DPZdUolNjV' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 26399922.99743 to 26399920.99743
+ 149545601043747358 from 3600000 to 3600001

16 'M4sm0Z6IfJIbE10s' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 26399920.99743 to 26399918.99743
+ 149545601043747358 from 3600001 to 3600002

16 'VuIeINlU2WNLY8d1' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 26399918.99743 to 26399916.99743
+ 149545601043747358 from 3600002 to 3600003

16 'K0SnOZuQYERCUJSu' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 26399916.99743 to 26399914.99743
+ 149545601043747358 from 3600003 to 3600004

16 'DOA4A9QlydPP32VO' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 26399914.99743 to 26399912.99743
+ 149545601043747358 from 3600004 to 3600005

16 'CeAoDOdLWGiNEVNu' '1092564458935116408' '149545601043747358' 1500000 1
- 1092564458935116408 from 26399912.99743 to 24899911.99743
+ 149545601043747358 from 3600005 to 5100005

16 'tpogMdWoA8RdEtC8' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 24899911.99743 to 24899909.99743
+ 149545601043747358 from 5100005 to 5100006

16 'wnAKTiraGovXcS5b' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 24899909.99743 to 24899907.99743
+ 149545601043747358 from 5100006 to 5100007

16 'YQ1eYtNTYgraJahR' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 24899907.99743 to 24899905.99743
+ 149545601043747358 from 5100007 to 5100008

BLOCK 17
17 'D58577RC162ts88Y' '1092564458935116408' '149545601043747358' 1 1
- 1092564458935116408 from 24899905.99743 to 24899903.99743
+ 149545601043747358 from 5100008 to 5100009

17 'R0mf9vzTvoPTWnua' '1092564458935116408' '149545601043747358' 100 1
- 1092564458935116408 from 24899903.99743 to 24899802.99743
+ 149545601043747358 from 5100009 to 5100109

17 'uicUABnQvMSRZUr9' '1092564458935116408' '149545601043747358' 50 1
- 1092564458935116408 from 24899802.99743 to 24899751.99743
+ 149545601043747358 from 5100109 to 5100159

17 'HIix69j0llnCiyuq' '1092564458935116408' '149545601043747358' 500 1
- 1092564458935116408 from 24899751.99743 to 24899250.99743
+ 149545601043747358 from 5100159 to 5100659

17 'blnwEcQEvwIHLKNV' '1092564458935116408' '149545601043747358' 186.59814 1
- 1092564458935116408 from 24899250.99743 to 24899063.39929
+ 149545601043747358 from 5100659 to 5100845.59814

BLOCK 18
18 'iGvnagEQcUgbudzz' '1092564458935116408' '149545601043747358' 65 1
- 1092564458935116408 from 24899063.39929 to 24898997.39929
+ 149545601043747358 from 5100845.59814 to 5100910.59814

BLOCK 19
19 'Yqzz6LuA81eI0xyb' '149545601043747358' '149545601043747358' 1 1
- 149545601043747358 from 5100910.59814 to 5100908.59814
+ 149545601043747358 from 5100908.59814 to 5100909.59814

19 '5ryM32A94Bgbwigw' '149545601043747358' '149545601043747359' 1 1
- 149545601043747358 from 5100909.59814 to 5100907.59814
+ 149545601043747359 from 0 to 1

19 'LfQ6uclp4aXga24q' '149545601043747358' '149545601043747350' 10 1
- 149545601043747358 from 5100907.59814 to 5100896.59814
+ 149545601043747350 from 0 to 10

BLOCK 20
20 'KtM9vLUYaGRBeyNK' '149545601043747358' '149545601043747350' 100 1
- 149545601043747358 from 5100896.59814 to 5100795.59814
+ 149545601043747350 from 10 to 110

BLOCK 21
21 'lKgiJF6qNhIRR8r9' '149545601043747358' '149545601043747350' 10 1
- 149545601043747358 from 5100795.59814 to 5100784.59814
+ 149545601043747350 from 110 to 120

BLOCK 22
22 'eANSaR2I4MwbvCyA' '15007997926042764084' '7520636997306874572' 500000 1
- 15007997926042764084 from 600000000 to 599499999
+ 7520636997306874572 from 0 to 500000

BLOCK 23
23 'QSpHPw96cHmrvhNb' '14931191424261653564' '17591617551191551229' 0.01 1
- 14931191424261653564 from 9.35 to 8.34
+ 17591617551191551229 from 9999986.65 to 9999986.66

BLOCK 24
24 'Ohjp28GNd5uhbiTw' '15007997926042764084' '5921881255187408995' 500000 1
- 15007997926042764084 from 599499999 to 598999998
+ 5921881255187408995 from 0 to 500000

BLOCK 25
25 '1XtuacA8WypYXCkP' '15007997926042764084' '18417060698680254365' 500000 1
- 15007997926042764084 from 598999998 to 598499997
+ 18417060698680254365 from 0 to 500000

BLOCK 26
26 'eSdQylccrSAKfDmA' '15007997926042764084' '6943953658916908917' 500000 1
- 15007997926042764084 from 598499997 to 597999996
+ 6943953658916908917 from 0 to 500000

BLOCK 27
27 'tM6U0khOPFq8z2QD' '15007997926042764084' '3863393017664103565' 500000 1
- 15007997926042764084 from 597999996 to 597499995
+ 3863393017664103565 from 0 to 500000

BLOCK 28
28 'CbhgnMmZuWxdWwDc' '15007997926042764084' '17689260977368600948' 500000 1
- 15007997926042764084 from 597499995 to 596999994
+ 17689260977368600948 from 0 to 500000

BLOCK 29
29 'fjrlTmLBKVQM7rSL' '15007997926042764084' '18098809587477536662' 100 1
- 15007997926042764084 from 596999994 to 596999893
+ 18098809587477536662 from 0 to 100

BLOCK 30
30 'VNsbC8XgWQhdaRRw' '15007997926042764084' '18098809587477536662' 499900 1
- 15007997926042764084 from 596999893 to 596499992
+ 18098809587477536662 from 100 to 500000

BLOCK 31
31 'yKbpr912KNh759QR' '16711743091738550527' '18098809587477536662' 1 1
- 16711743091738550527 from 11.63601 to 9.63601
+ 18098809587477536662 from 500000 to 500001

31 'yyUSIcx5FicN2hXH' '16711743091738550527' '18098809587477536662' 3 1
- 16711743091738550527 from 9.63601 to 5.63601
+ 18098809587477536662 from 500001 to 500004

31 'u0gLl0pvV5JDCS4z' '16711743091738550527' '18098809587477536662' 1 1
- 16711743091738550527 from 5.63601 to 3.63601
+ 18098809587477536662 from 500004 to 500005

BLOCK 32
32 'AujjH5bluPW3cMH7' '16711743091738550527' '16711743091738550527' 1 1
- 16711743091738550527 from 3.63601 to 1.63601
+ 16711743091738550527 from 1.63601 to 2.63601

32 'yyOyWwySqObBQ1v8' '16711743091738550527' '16711743091738550527' 1 1
- 16711743091738550527 from 2.63601 to 0.63601
+ 16711743091738550527 from 0.63601 to 1.63601

32 'Dn6SRgZSDiVf1943' '16711743091738550527' '16711743091738550527' 1 1
- 16711743091738550527 from 1.63601 to -0.36399
+ 16711743091738550527 from -0.36399 to 0.63601

32 '4dLkpDSWVBkOL6fW' '16711743091738550527' '16711743091738550527' 1 1
- 16711743091738550527 from 0.63601 to -1.36399
+ 16711743091738550527 from -1.36399 to -0.36399

BLOCK 33
33 'EazK9xqJXACaS0Jt' '16711743091738550527' '16711743091738550527' 1 1
- 16711743091738550527 from -0.36399 to -2.36399
+ 16711743091738550527 from -2.36399 to -1.36399

33 'uKVRyEiFv33IOool' '16711743091738550527' '16711743091738550527' 1 1
- 16711743091738550527 from -1.36399 to -3.36399
+ 16711743091738550527 from -3.36399 to -2.36399

BLOCK 34
34 'RNAo9RnyL5l8YCFq' '16711743091738550527' '16711743091738550526' 0.56 1
- 16711743091738550527 from -2.36399 to -3.92399
+ 16711743091738550526 from 0 to 0.56

BLOCK 35
35 'eUutmlF0vw2aGqyn' '1092564458935116408' '16711743091738550527' 50 1
- 1092564458935116408 from 24898997.39929 to 24898946.39929
+ 16711743091738550527 from -3.92399 to 46.07601

You can sum the ins and outs for the account itself from the data at http://nodemoney.com:19775/account/getAccountTransactions?accountId=14931191424261653564 and you'll clearly see that it has more outs and fees than ins!

Even if you look on the block explorer ledger and add it up yourself, you see the same.  This account has more node IN than OUT even before fees!

First you mess commission for distribution of coins commission has been disabled to 0.0001
By default it is 0.35%

You can send all of your balance plus some additional fee.  Unless the fee coins just get destroyed or something, this creates additional coins even if the original bug to create net negative balance was fixed!

[SillkRoad]

You can sum the ins and outs for the account itself from the data at http://nodemoney.com:19775/account/getAccountTransactions?accountId=14931191424261653564 and you'll clearly see that it has more outs and fees than ins!

Even if you look on the block explorer ledger and add it up yourself, you see the same.  This account has more node IN than OUT even before fees!

were units that it generated, the initial fee for the generation unit was 1 fee, then 0.35%, now temporarily 0.00001, tomorrow I will add here that even blocks it generated, and it will be seen that the balance is actually positive

You can go on 1234567890 and see that he is still positive, you can try to send more than is in the account, given the fact that the Commission now 0.00001

[Hueristic]

I've noticed there is dust for every password so you could conceivably make some cash scooping it all up. Of course you might stumble onto someones account doing that as well. Does the account lock to your IP when you create it?

There is not dust in every account, I just stumbled onto an obvious password.

Really? I tried 4 variations on my password when it went to the wrong acct and every one had dust.

[SillkRoad]

I've noticed there is dust for every password so you could conceivably make some cash scooping it all up. Of course you might stumble onto someones account doing that as well. Does the account lock to your IP when you create it?

There is not dust in every account, I just stumbled onto an obvious password.

Really? I tried 4 variations on my password when it went to the wrong acct and every one had dust.

if one of the users were online at the time when we were doing the distribution of the coins, the account number could generate block, and here you see the result

Look at block # 272-275
and account number: password145

[HunterMinerCrafter]

You can sum the ins and outs for the account itself from the data at http://nodemoney.com:19775/account/getAccountTransactions?accountId=14931191424261653564 and you'll clearly see that it has more outs and fees than ins!

Even if you look on the block explorer ledger and add it up yourself, you see the same.  This account has more node IN than OUT even before fees!

were units that it generated, the initial fee for the generation unit was 1 fee, then 0.35%, now temporarily 0.00001, tomorrow I will add here that even blocks it generated, and it will be seen that the balance is actually positive

You can go on 1234567890 and see that he is still positive, it may try to send more than is in the account, given the fact that the Commission now 0.00001

I'm not sure that I understand anything of what you just said.

It is also interesting to note that the data from the site and the data shown by the block explorer differ on the details surrounding block 32, but both show a net negative balance on the account.

Yes, I left some of the dust that I found on "1234567890." Since you know what the plaintext of the account that I found my dust on was this would indicate that you know everyones' plaintext passwords.  I would hope that no-one reused a password from anything important.

I haven't been doing any of my experiments on the "1234567890" account, though, so I'm not sure why it still having a balance would be relevant.  Also, none of my other accounts were ever taken negative, so you might have misunderstood me.  What I mean is not that I can make a negative balance on an account now but that if one transfers 100% of their balance with no fee set, 100% of the balance arrives but the ledger shows a fee having been paid in addition, presumably creating (currently) 0.00001 new node in the hands of the miner each time.  I'm sure some mining node could transfer 100% of their own balance with some huge fee attached (since the "network" somehow doesn't seem to check if the fee is both valid and available) and profit immensely by mining the block.  Even if they can't set fee more than 0.00001, they could just mine lots and lots of blocks since it appears that they have every capability to mine blocks instantly.

This is assuming there is any actual mining process occurring "behind the scenes" at all, of course.  I'm increasingly skeptical.  If there is currently a miner collecting fees, what is the address at which it currently does so, so we can see if it also balances or not in the explorer?  What exactly is the claim algorithm, which in the "marketing materials" is left incredibly vague, and for which there appears to be no real information coming out of the system itself?  Also, logically it would seem that if all coins up to cap are already held under key, there can be no systematic staking interest paid out and only claim of fees.... so what is the proposed incentive to mine without high value transactions already constantly occurring?  Where can we see the "proof" part of the proof-of-work and/or proof-of-stake that is occurring?  Why should we think that any aspect of this system isn't just a bad, clunky pay-pal?  (Closed system on a centralized server, over-reaching administrative controls, etc.)

Also, why exactly couldn't all of the "distribution" be done at once?  Why this slow account-by-account re-disbursement?

I'm sure that some more detailed explanations would be appreciated by your stakeholders.

[SillkRoad]

I'm not sure that I understand anything of what you just said.

It is also interesting to note that the data from the site and the data shown by the block explorer differ on the details surrounding block 32, but both show a net negative balance on the account.

Yes, I left some of the dust that I found on "1234567890." Since you know what the plaintext of the account that I found my dust on was this would indicate that you know everyones' plaintext passwords.  I would hope that no-one reused a password from anything important.

I haven't been doing any of my experiments on the "1234567890" account, though, so I'm not sure why it still having a balance would be relevant.  Also, none of my other accounts were ever taken negative, so you might have misunderstood me.  What I mean is not that I can make a negative balance on an account now but that if one transfers 100% of their balance with no fee set, 100% of the balance arrives but the ledger shows a fee having been paid in addition, presumably creating (currently) 0.00001 new node in the hands of the miner each time.  I'm sure some mining node could transfer 100% of their own balance with some huge fee attached (since the "network" somehow doesn't seem to check if the fee is both valid and available) and profit immensely by mining the block.  Even if they can't set fee more than 0.00001, they could just mine lots and lots of blocks since it appears that they have every capability to mine blocks instantly.

This is assuming there is any actual mining process occurring "behind the scenes" at all, of course.  I'm increasingly skeptical.  If there is currently a miner collecting fees, what is the address at which it currently does so, so we can see if it also balances or not in the explorer?  What exactly is the claim algorithm, which in the "marketing materials" is left incredibly vague, and for which there appears to be no real information coming out of the system itself?  Also, logically it would seem that if all coins up to cap are already held under key, there can be no systematic staking interest paid out and only claim of fees.... so what is the proposed incentive to mine without high value transactions already constantly occurring?  Where can we see the "proof" part of the proof-of-work and/or proof-of-stake that is occurring?  Why should we think that any aspect of this system isn't just a bad, clunky pay-pal?  (Closed system on a centralized server, over-reaching administrative controls, etc.)

Also, why exactly couldn't all of the "distribution" be done at once?  Why this slow account-by-account re-disbursement?

I'm sure that some more detailed explanations would be appreciated by your stakeholders.

Firstly, we have reduced the commission initially for distribution of coins. We did not want to remake "Forge", so disable some functionality and reduced fees. In the client will work in normal mode. We also wanted to check on the server generating block. We not only distribute the coins, but also test

Secondly soon client and you will see for yourself. Each participant will be able to take in beta testing. Of course there are bugs, we will test and encourage users for any errors

Once again I repeat your balance is not correct, you can not see all the blocks

Look at block # 272-275
and account number: password145 (11875288750812311935)  http://nodemoney.com:19775
and
http://nodemoney.com:19775/blockchainexpl/

[HunterMinerCrafter]

Once again I repeat your balance is not correct, you can not see all the blocks

Huh?  What blocks can't be seen, and wouldn't that just mean that there are even more coins??  (Since the blocks I "can" see do account for every coin, plus the few extra!)

I really don't understand anything of what you're trying to say, other than the "you will see."  I really would love to see for myself!  I started this whole discussion with "I'd like to see source."

Which part of that 35 block parse is not correct?  It shows the balance of your account going negative, and even your own site and block explorer agree with it.  What, specifically, is not correct?  If my chain parse, your site's account history, and your explorer all agree that your account went negative then, as far as anyone can be concerned, your account went negative.

[SillkRoad]

Once again I repeat your balance is not correct, you can not see all the blocks

Huh?  What blocks can't be seen, and wouldn't that just mean that there are even more coins??  (Since the blocks I "can" see do account for every coin, plus the few extra!)

I really don't understand anything of what you're trying to say, other than the "you will see."  I really would love to see for myself!  I started this whole discussion with "I'd like to see source."

Which part of that 35 block parse is not correct?  It shows the balance of your account going negative, and even your own site and block explorer agree with it.  What, specifically, is not correct?  If my chain parse, your site's account history, and your explorer all agree that your account went negative then, as far as anyone can be concerned, your account went negative.

I do not understand you,
You are doing wrong calculation error you have, so I'll give you tomorrow for the correct calculation of your blocks

source code will be opened after the beta testing

if you want to help us, you can join us
we will reveal to you a few lines

[HunterMinerCrafter]

I do not understand you,
You are doing wrong calculation error you have, so I'll give you tomorrow for the correct calculation of your blocks

You've said my conclusion is wrong several times now, but have not yet explained how it can be wrong.

Here is the data straight from your block explorer for 14931191424261653564

Code:

id	Sender	Recipient	Ammount	Fee
12845206835269364784	14931191424261653564	15452014960459345794	0.0922	0.00001
5018937612377503329	14931191424261653564	6618192569618682016	1	0.00001
5700905546718490151	14931191424261653564	17591617551191551229	0.01	0.00001
13484712660724554178	14931191424261653564	17591617551191551229	0.01	0.00004
743373330916963902	14931191424261653564	17591617551191551229	0.01	0.00004
5714408362752147383	14931191424261653564	17591617551191551229	0.01	0.00004
12823647786059863083	14931191424261653564	17591617551191551229	0.01	0.00004
13442360466351869795	14931191424261653564	17591617551191551229	0.01	0.00004
14303885377400851356	14931191424261653564	17591617551191551229	0.1	0.00035
11174689921170464920	14931191424261653564	17591617551191551229	0.01	0.00004
8980591579813928523	14931191424261653564	17591617551191551229	0.001	0.00001
14394236852179174845	14931191424261653564	17591617551191551229	0.001	0.00001
2326980602599604324	14931191424261653564	17591617551191551229	11	0.0385
15442885102068069929	14931191424261653564	17591617551191551229	0.01	0.00004
10749341276028122134	14931191424261653564	17591617551191551229	0.1	1
17440046058446214449	14931191424261653564	17591617551191551229	0.01	1
17540076683096205620	17591617551191551229	14931191424261653564	0.02	1
1657007062373292605	17591617551191551229	14931191424261653564	0.02	1
17495854921759089114	17591617551191551229	14931191424261653564	0.02	1
7349136027811136473	14931191424261653564	17591617551191551229	0.01	1
12884179395091139578	17591617551191551229	14931191424261653564	10.15	0
7723897683554645791	17591617551191551229	14931191424261653564	0.15	0

Sum of inputs is 10.36 = 0.15 + 10.15 + 0.02 + 0.02 + 0.02
Sum of outputs is 12.3942 = 0.0922 + 1 + 0.01 + 0.01 + 0.01 + 0.01 + 0.01 + 0.01 + 0.1 + 0.01 + 0.001 + 0.001 + 11 + 0.01 + 0.1 + 0.01 + 0.01
Sum of fees is 3.03918 = 0.00001 + 0.00001 + 0.00001 + 0.00004 + 0.00004 + 0.00004 + 0.00004 + 0.00004 + 0.00035 + 0.00004 + 0.00001 + 0.00001 + 0.0385 + 0.00004 + 1 + 1 + 1
Balance is -5.07338 = 10.36 - (12.3942+3.03918)

Which of these calculations is the wrong one?  (I really am running out of reasonable ways to do the "show my work" thing here...)

source code will be opened after the beta testing

if you want to help us, you can join us
we will reveal to you a few lines

I'd love to review whatever source code you'd make available to me!

[SillkRoad]

Sum of inputs is 10.36 = 0.15 + 10.15 + 0.02 + 0.02 + 0.02
Sum of outputs is 12.3942 = 0.0922 + 1 + 0.01 + 0.01 + 0.01 + 0.01 + 0.01 + 0.01 + 0.1 + 0.01 + 0.001 + 0.001 + 11 + 0.01 + 0.1 + 0.01 + 0.01
Sum of fees is 3.03918 = 0.00001 + 0.00001 + 0.00001 + 0.00004 + 0.00004 + 0.00004 + 0.00004 + 0.00004 + 0.00035 + 0.00004 + 0.00001 + 0.00001 + 0.0385 + 0.00004 + 1 + 1 + 1
Balance is -5.07338 = 10.36 - (12.3942+3.03918)

Which of these calculations is the wrong one?  (I really am running out of reasonable ways to do the "show my work" thing here...)

You logged into the account 14931191424261653564?
password: 1234567890

You see a negative balance?

I say mistake in commissions since it was changed for several times for the distribution of coins



also you miss this moment that this account  generated block
Commission came to this number account block


closed

[HunterMinerCrafter]

I say mistake in commissions since it was changed for several times for the distribution of coins

Then it must be a mistake that is coincidentally in both my code and the block explorer code!  

if this is the only account was logged on the server, and it has generated block
Commission came to this number account back

closed

Yes, the summary of the net balance for the account shows positive, but the account's own transaction history sums up to a negative, so if the summary number is the correct one then the server itself also coincidentally shares this bug in the history!  (Or, in other words, the server disagrees with itself about this account, in any case.)

If this is 5 coins coming in from elsewhere, where are they coming from?  There weren't other transactions in the block to collect fees from, unless the miner moved coins to another "otherwise disconnected from genesis addresses" location, which you could provide the missing tx for.  Any other coins not "already" collected in fees at that time were still accounted for.  Why wouldn't they show some different transaction type or whatnot? If these are some fee collections from staking then they are indistinguishable from other transactions!  Why do total account balances sum to a surplus precisely matching the difference of fees?  Simply showing the mining address collecting all other fees would easily answer this!

I'd really like to see some answer instead of just another assertion that I'm wrong without any explanation, but to be honest I'm quickly losing interest in the whole matter.  Being a huge fan of nodejs I was really hoping to see a great coin here, but I have every indication (so far) that I'm going to be left disappointed yet again.

[jly77]

I am in the list. How can I get my coins? Thanks.

[jly77]

I am in the list. How can I get my coins? Thanks.

My node account is 16788356351633443172, but I don't see my account ID on the list, what should I do now?