BitShares Forum

Other => Graveyard => KeyID => Topic started by: toast on September 26, 2014, 05:42:11 pm

Title: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 26, 2014, 05:42:11 pm
This is the thread I will point to if someone complains about having the wrong allocation after the fact!

https://raw.githubusercontent.com/keyid/keyid/master/libraries/blockchain/genesis.json
https://raw.githubusercontent.com/keyid/keyid/2332af34f91677f8b489032a9fb5dd5de42719f3/libraries/blockchain/genesis_keyid.json
https://raw.githubusercontent.com/keyid/keyid/e2bb322fd63e44a58fcef4aa464ddaca557f1b55/libraries/blockchain/genesis_keyid.json

Note - keyhotee AGS was not honored!  This allocation was announced *after* keyhotee donations ended, and the BTSX stake more than paid back for the donation. We don't owe them anything and honoring it is too much manual work. This stake is split proportionally to all other balances.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 26, 2014, 05:51:12 pm
I will use these substitutions after I check signatures:

https://bitsharestalk.org/index.php?topic=4748.0
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: emski on September 26, 2014, 06:10:48 pm
I see numbers. What should I expect?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 26, 2014, 06:18:57 pm
AGS * 1000
PTS * ~1176  (honestly not sure, never checked the supply on the PTS block:   https://coinplorer.com/PTS/Blocks/0000001418b7dbf283dc1e7454fafdafc8934ba8640c263ee77de92e5eca74ee )

+ a little extra from founder AGS
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: emski on September 26, 2014, 06:26:48 pm
So something like 117600000000 * <My PTS at snapshot time> ?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 26, 2014, 06:30:06 pm
So something like 117600000000 * <My PTS at snapshot time> ?

Yep, plus a little extra
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: emski on September 26, 2014, 06:32:31 pm
Looks good for me.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: Riverhead on September 26, 2014, 06:47:33 pm
Within 1.3% of expected; the error is an overage. Nice work, that's spread across about a half dozen or so addresses.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: hadrian on September 26, 2014, 09:35:26 pm
Something's not right with address 14fXr2UTa17CadcZ911N7TBFqMLpqsfNae

The same problem arose with Lottoshares here: https://bitsharestalk.org/index.php?topic=4879.msg64977#msg64977 (https://bitsharestalk.org/index.php?topic=4879.msg64977#msg64977)

AGS Explorer shows 566.53948028 AGS
Your number for this address is 56596237510000

The numbers aren't THAT far out, but other addresses don't seem to have this problem.
I'm curious as to the cause of the discrepancy...
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: Brekyrself on September 27, 2014, 12:54:36 am
Looks about right when dividing what you provided in the github file by 117600000000.  Nice job, can't wait!
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: spoonman on September 27, 2014, 01:05:09 am
Should be able to import private keys from btsx? I want to make sure I can import brian this time.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 27, 2014, 07:18:25 am
It seems agsexplorer only show the total AGS of all related PTS addresses, instead of individual address.
It is a bit difficult to double check with the DNS allocation.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 27, 2014, 07:38:33 am
Besides, does the genesis allocation accounts for bounty?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 27, 2014, 09:53:12 am
Just want to clarify. The genesis block allocation contains both the AGS and PTS allocations.
So if I see the allocation associated with a PTS address in the json file, it is the sum of the allocation for AGS (donated from that same PTS address) plus the allocation to the same PTS (holdiing during snapshot), am I right?

Or it only accounts for AGS allocation?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: testz on September 27, 2014, 09:54:48 am
Just want to clarify. The genesis block allocation contains both the AGS and PTS allocations.
So if I see the allocation associated with a PTS address in the json file, it is the sum of the allocation for AGS (donated from that same PTS address) plus the allocation to the same PTS (holdiing during snapshot), am I right?

Yes
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on September 27, 2014, 09:55:43 am
Just want to clarify. The genesis block allocation contains both the AGS and PTS allocations.
So if I see the allocation associated with a PTS address in the json file, it is the sum of the allocation for AGS (donated from that same PTS address) plus the allocation to the same PTS (holdiing during snapshot), am I right?
assuming your have left some PTS in an address you also used to donate to AGS from .. then I would say so .. yes
those allocations should also be listed accordingly @ agsexplorer.com AFAIK
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 27, 2014, 09:59:49 am
Just want to clarify. The genesis block allocation contains both the AGS and PTS allocations.
So if I see the allocation associated with a PTS address in the json file, it is the sum of the allocation for AGS (donated from that same PTS address) plus the allocation to the same PTS (holdiing during snapshot), am I right?

Yes

If that is the case, it seems to there is a discrepancy. I wrote a python to scan and sum all my PTS addressess in the genesis allocation. It is less than I expected. It seems to me it only accounts for AGS allocation. May be I missed something.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on September 27, 2014, 10:01:43 am
have you had a change in your pts position since the snapshot?

could you share the script?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: testz on September 27, 2014, 10:02:51 am
Just want to clarify. The genesis block allocation contains both the AGS and PTS allocations.
So if I see the allocation associated with a PTS address in the json file, it is the sum of the allocation for AGS (donated from that same PTS address) plus the allocation to the same PTS (holdiing during snapshot), am I right?

Yes

If that is the case, it seems to there is a discrepancy. I wrote a python to scan and sum all my PTS addressess in the genesis allocation. It is less than I expected. It seems to me it only accounts for AGS allocation. May be I missed something.

Double check your AGS allocation with http://www1.agsexplorer.com
If your address in json has, as example 12345678901234 this mean you has 123.45678901234 AGS and http://www1.agsexplorer.com should show it.
If you has more for specific address, probably this address has AGS and PTS at snapshot.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on September 27, 2014, 10:09:29 am
Hug?
Code: [Select]
235800         [
235801             "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
235802             1177308757                                                                                                                                                                                                     
235803             47092115
235804         ],
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 27, 2014, 10:10:20 am
have you had a change in your pts position since the snapshot?

could you share the script?

Here is the python code. You may need to install the required modules.
Just put the output of "listaddressgroupings" as a file in the same folder, e.g. "pts-listaddressgroupings.json"
and pass the name of the file containing the genesis block as command line option to the program.

Quote
#
# dns-alloc.py  [genesis_json]
#
# This program intends to extract addresses from bitcoin-qt (or protoshares-qt) debug window command
# listaddressgrouppings. Then it looks up Bitshares DNS genesis block (allocation of DNS to AGS (PTS|BTC)
# and PTS. It lists the DNS allocation for each address and cumulate the sum.
# Save your listaddressgroupings to a file like "pts-listaddressgroupings.json". The program will
# scans all matched .json file. The genesis json is input as the command line option.
#
# ffwong
 


import sys
import json
from sys import exit
from pprint import pprint
import glob


def recur_addr(alist, btclist):
    for i in range(0,len(alist)):   
        if isinstance(alist, list):     
            recur_addr(alist, btclist)
        elif isinstance(alist, str) and len(alist)>30 and (alist[0]=='1' or alist[0]=='P'):
            #pprint (alist)
            btclist.append(alist)
   

###### main ######

scaleup = 1  # DNS scale up factor (if any)

wallets = glob.glob('*-listaddressgroupings.json')
filecnt = len(wallets)

genesis_json = open(sys.argv[1])  # change the filename is file changed
genesis_dict = json.load(genesis_json)
genesis      = genesis_dict['balances']  # list of list

for i in range (0, filecnt):
    jfilename = wallets

    # Load json text file and extract all addresses recursively
    json_data = open(jfilename)
    addrlist = json.load(json_data)

    btclist = []
    recur_addr(addrlist,btclist)
    json_data.close()

    addrcnt      = len(btclist)
    allocnt      = len(genesis)
    start        = 0
    dns_sum     = 0
    for i in range(0, addrcnt): # for each address, look up the genesis block
        allocation = 0       
        for j in range(0, allocnt):
            if genesis[j][0] == btclist:       
                allocation  = genesis[j][1]
                msg = '%40s: %16.8f DNS' % (genesis[j][0], allocation/100000000*scaleup)
                print (msg)
                break
        dns_sum += allocation   
    msg = ('Wallet %18s: [address count: %3d]   [amount: %16.8f DNS]' % \
          (jfilename.replace('-listaddressgroupings.json',''), len(btclist), dns_sum/100000000*scaleup))   
    pprint (msg)  # convert satoshi -> DNS

Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 27, 2014, 10:11:15 am
Hug?
Code: [Select]
235800         [
235801             "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
235802             1177308757                                                                                                                                                                                                     
235803             47092115
235804         ],

Yes, I met this bug or typo as I run my python script as well, you need to manually fix it.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on September 27, 2014, 10:13:01 am
Hug?
Code: [Select]
235800         [
235801             "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
235802             1177308757                                                                                                                                                                                                     
235803             47092115
235804         ],

Yes, I met this bug or typo as I run my python script as well, you need to manually fix it.

and toast should fix it too .. however .. no idea if I am supposed to just add them up!?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 27, 2014, 10:22:04 am
have you had a change in your pts position since the snapshot?


@xeroc, you are right, I did move my coin to a new wallet right before the snapshot. And I forgot to scan that new wallet addresses. Now, after including that listaddressgroupings from this new wallet. The sum is correct. I can confirm (at least my allocation) that the genesis block allocation contains AGS (both from BTC and PTS donations) and PTS (during snapshot time) allocation. Thanks.  ;)
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on September 27, 2014, 10:23:53 am
Just wanted to run the script of
https://bitsharestalk.org/index.php?topic=9283.0
on the genesis block but couldn't find the total supply (at launch) to make the numbers right!?
is the supply announced? I just know about the distribution :(
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: Akado on September 27, 2014, 10:53:55 am
my numbers seem to be off? It seems to show i have only 151 pts/ags but i was supposed to have some more?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 27, 2014, 06:44:43 pm
Just wanted to run the script of
https://bitsharestalk.org/index.php?topic=9283.0
on the genesis block but couldn't find the total supply (at launch) to make the numbers right!?
is the supply announced? I just know about the distribution :(

Initial supply is 5bn.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 27, 2014, 06:45:51 pm
Just wanted to run the script of
https://bitsharestalk.org/index.php?topic=9283.0
on the genesis block but couldn't find the total supply (at launch) to make the numbers right!?
is the supply announced? I just know about the distribution :(

Initial supply is 5bn.

I think genesis block will add up to something below 5bn because keyhotee is excluded so your balance will be scaled up.

I think I better just allocate keyhotee AGS to a key and then burn it on launch so that there isn't this small scaling.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: hadrian on September 27, 2014, 07:15:41 pm
Something's not right with address 14fXr2UTa17CadcZ911N7TBFqMLpqsfNae

The same problem arose with Lottoshares here: https://bitsharestalk.org/index.php?topic=4879.msg64977#msg64977 (https://bitsharestalk.org/index.php?topic=4879.msg64977#msg64977)

AGS Explorer shows 566.53948028 AGS
Your number for this address is 56596237510000

The numbers aren't THAT far out, but other addresses don't seem to have this problem.
I'm curious as to the cause of the discrepancy...

Is it bad form to quote myself? Dunno...

Anyway, is there an explanation for the discrepancy for address 14fXr2UTa17CadcZ911N7TBFqMLpqsfNae?

The figures on AGSexplorer don't seem to match those reported for the genesis blocks.

It's happened with LottoShares and DNS. Will it occur with all DACs? It bothers me because I don't understand it...
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 27, 2014, 07:26:54 pm
Sounds like a bounty.. Who wants to recreate the snapshot?

There are several DACs coming up soon, I feel like we at least need an "official" AGS distribution
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: vikram on September 28, 2014, 02:03:50 am
It seems agsexplorer only show the total AGS of all related PTS addresses, instead of individual address.
It is a bit difficult to double check with the DNS allocation.

I have 2 BTC addresses, and 5 PTS addresses all with only AGS allocations. After taking the quoted annoyance with AGSExplorer into account, all 7 of my addresses are exactly represented (modulo rounding errors) as ( 100,000,000,000 * AGSExplorer_value ) in this commit's genesis block: https://github.com/keyid/keyid/blob/805949683d21dd4d02a1e8e109929411611f1844/libraries/blockchain/genesis.json

All of these checks are meaningless, however, until somebody sums all of the balances in the file and verifies the total supply, and also until the file is verified to be well-formed JSON; see e.g.:
Hug?
Code: [Select]
235800         [
235801             "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
235802             1177308757                                                                                                                                                                                                     
235803             47092115
235804         ],
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 28, 2014, 04:48:25 am

I have 2 BTC addresses, and 5 PTS addresses all with only AGS allocations. After taking the quoted annoyance with AGSExplorer into account, all 7 of my addresses are exactly represented (modulo rounding errors) as ( 100,000,000,000 * AGSExplorer_value ) in this commit's genesis block: https://github.com/keyid/keyid/blob/805949683d21dd4d02a1e8e109929411611f1844/libraries/blockchain/genesis.json

All of these checks are meaningless, however, until somebody sums all of the balances in the file and verifies the total supply, and also until the file is verified to be well-formed JSON; see e.g.:
Hug?
Code: [Select]
235800         [
235801             "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
235802             1177308757                                                                                                                                                                                                     
235803             47092115
235804         ],

The typo above seems to be the only place with error in the json file.

By simply concatenating the digits at the above error and  modifying my script to sum up the total in the genesis block json, total sum of allocation is   6,177,308,745.22691250

By removing the first line of digits and keeping only the second line of digits at the above error, I got the total sum of allocation: 4,999,999,988.22691250. This seems to be more correct.



It may not be equivalent to the total supply.

Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: boombastic on September 28, 2014, 04:51:59 am
It seems agsexplorer only show the total AGS of all related PTS addresses, instead of individual address.
It is a bit difficult to double check with the DNS allocation.

On the balance page, there's a link to toggle "merged/separate" view on the right hand side of the look up address.  By default, merged view is displayed, you can switch to separate view for your purpose.

Sample link:
http://www1.agsexplorer.com/balances/xxxxxx?view=seperate
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: ffwong on September 28, 2014, 04:57:00 am
It seems agsexplorer only show the total AGS of all related PTS addresses, instead of individual address.
It is a bit difficult to double check with the DNS allocation.

On the balance page, there's a link to toggle "merged/separate" view on the right hand side of the look up address.  By default, merged view is displayed, you can switch to separate view for your purpose.

Sample link:
http://www1.agsexplorer.com/balances/xxxxxx?view=seperate

Thanks. This is useful.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: clar on September 28, 2014, 09:12:28 am

I have 2 BTC addresses, and 5 PTS addresses all with only AGS allocations. After taking the quoted annoyance with AGSExplorer into account, all 7 of my addresses are exactly represented (modulo rounding errors) as ( 100,000,000,000 * AGSExplorer_value ) in this commit's genesis block: https://github.com/keyid/keyid/blob/805949683d21dd4d02a1e8e109929411611f1844/libraries/blockchain/genesis.json

All of these checks are meaningless, however, until somebody sums all of the balances in the file and verifies the total supply, and also until the file is verified to be well-formed JSON; see e.g.:
Hug?
Code: [Select]
235800         [
235801             "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
235802             1177308757                                                                                                                                                                                                     
235803             47092115
235804         ],

The typo above seems to be the only place with error in the json file.

By simply concatenating the digits at the above error and  modifying my script to sum up the total in the genesis block json, total sum of allocation is   6,177,308,745.22691250

By removing the first line of digits and keeping only the second line of digits at the above error, I got the total sum of allocation: 4,999,999,988.22691250. This seems to be more correct.



It may not be equivalent to the total supply.

toast used this website (http://ptsags.quisquis.de/ ) to generate the genesis file, and the total sum should equal to 5,000,000,000 including dev fund.

" 47092115" belongs to ["PmmFHqcApEPqibJEzqvvBhduEaDwgn7LFQ",47092115] which is just beside ["PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",1177308757],
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: clar on September 28, 2014, 09:13:52 am
https://bitsharestalk.org/index.php?topic=7251.msg99579#msg99579
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on September 28, 2014, 10:06:35 am
Code: [Select]
--------------------------------------------------------------------------------
Total 5000000000.0 available:    5,000,000,000.00000000
--------------------------------------------------------------------------------
top 10 addresses collective percentage
--------------------------------------------------------------------------------
top    1 addresses collectively own     273,379,229 DNS (  5.47%)
top    2 addresses collectively own     473,379,229 DNS (  9.47%)
top    3 addresses collectively own     673,379,229 DNS ( 13.47%)
top    4 addresses collectively own     873,379,229 DNS ( 17.47%)
top    5 addresses collectively own   1,073,379,229 DNS ( 21.47%)
top    6 addresses collectively own   1,273,379,229 DNS ( 25.47%)
top    7 addresses collectively own   1,424,191,726 DNS ( 28.48%)
top    8 addresses collectively own   1,486,052,280 DNS ( 29.72%)
top    9 addresses collectively own   1,544,917,424 DNS ( 30.90%)
--------------------------------------------------------------------------------
top 10 addresses individual percentage
--------------------------------------------------------------------------------
top    1 addresse individually owns     273,379,229 DNS (  5.47%)
top    2 addresse individually owns     200,000,000 DNS (  4.00%)
top    3 addresse individually owns     200,000,000 DNS (  4.00%)
top    4 addresse individually owns     200,000,000 DNS (  4.00%)
top    5 addresse individually owns     200,000,000 DNS (  4.00%)
top    6 addresse individually owns     200,000,000 DNS (  4.00%)
top    7 addresse individually owns     150,812,498 DNS (  3.02%)
top    8 addresse individually owns      61,860,554 DNS (  1.24%)
top    9 addresse individually owns      58,865,144 DNS (  1.18%)
--------------------------------------------------------------------------------
address/amount distribution
--------------------------------------------------------------------------------
address with >             10 DNS:   46,242
address with >             30 DNS:   39,099
address with >             50 DNS:   37,093
address with >             70 DNS:   35,734
address with >             90 DNS:   34,789
address with >            100 DNS:   34,194
address with >            300 DNS:   28,921
address with >            500 DNS:   27,182
address with >            700 DNS:   25,994
address with >            900 DNS:   25,141
address with >          1,000 DNS:   24,771
address with >          3,000 DNS:   17,651
address with >          5,000 DNS:   15,408
address with >          7,000 DNS:   14,143
address with >          9,000 DNS:   13,263
address with >         10,000 DNS:   12,894
address with >         30,000 DNS:    9,086
address with >         50,000 DNS:    6,448
address with >         70,000 DNS:    5,221
address with >         90,000 DNS:    4,580
address with >        100,000 DNS:    4,304
address with >        300,000 DNS:    1,929
address with >        500,000 DNS:    1,287
address with >        700,000 DNS:      908
address with >        900,000 DNS:      710
address with >      1,000,000 DNS:      627
address with >      3,000,000 DNS:      143
address with >      5,000,000 DNS:       96
address with >      7,000,000 DNS:       71
address with >      9,000,000 DNS:       60
address with >     10,000,000 DNS:       45
address with >     30,000,000 DNS:       12
address with >     50,000,000 DNS:       12
address with >     70,000,000 DNS:        7
address with >     90,000,000 DNS:        7
address with >    100,000,000 DNS:        7


(http://i.imgur.com/RkAXm3z.png)
(http://i.imgur.com/FTIPaE8.png)
(http://i.imgur.com/9ofOlie.png)

python3 script
https://github.com/xeroc/pytshares/blob/master/genesisStats.py
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: betax on September 29, 2014, 10:46:12 am
I have modified the orginal bitbalance to check the DNS allocation. It seems to be fine with a mixture of BTC, PTS AGS donation and very small amount of PTS.

http://bitbalance.azurewebsites.net/


Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 29, 2014, 02:48:33 pm

I have 2 BTC addresses, and 5 PTS addresses all with only AGS allocations. After taking the quoted annoyance with AGSExplorer into account, all 7 of my addresses are exactly represented (modulo rounding errors) as ( 100,000,000,000 * AGSExplorer_value ) in this commit's genesis block: https://github.com/keyid/keyid/blob/805949683d21dd4d02a1e8e109929411611f1844/libraries/blockchain/genesis.json

All of these checks are meaningless, however, until somebody sums all of the balances in the file and verifies the total supply, and also until the file is verified to be well-formed JSON; see e.g.:
Hug?
Code: [Select]
235800         [
235801             "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
235802             1177308757                                                                                                                                                                                                     
235803             47092115
235804         ],

The typo above seems to be the only place with error in the json file.

By simply concatenating the digits at the above error and  modifying my script to sum up the total in the genesis block json, total sum of allocation is   6,177,308,745.22691250

By removing the first line of digits and keeping only the second line of digits at the above error, I got the total sum of allocation: 4,999,999,988.22691250. This seems to be more correct.



It may not be equivalent to the total supply.

toast used this website (http://ptsags.quisquis.de/ ) to generate the genesis file, and the total sum should equal to 5,000,000,000 including dev fund.

" 47092115" belongs to ["PmmFHqcApEPqibJEzqvvBhduEaDwgn7LFQ",47092115] which is just beside ["PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",1177308757],

are you saying there should be both of them like this:

Code: [Select]
["PmmFHqcApEPqibJEzqvvBhduEaDwgn7LFQ",47092115],
["PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",1177308757]

Instead of

Code: [Select]
        [
            "PuTHy9uGtdHdJ9ch1kTtrLkGkTuHe7HwSR",
            1177308757
            47092115
        ],

?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 29, 2014, 03:14:17 pm
Thanks vikram and clar, I fixed that mistake and now the total is exactly 500000000000000000
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: 38PTSWarrior on September 29, 2014, 09:18:52 pm
I'm in. So nice feeling!

"PmJwbQBFssGK1yd1GLQb8hHswzyRkqqNzB",
8689302181000
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: deejay on September 30, 2014, 09:58:15 am
I dont' really understand this post. Is this json on githubusercontent containing the future coin distribution for the DNS project?

I own AGS and PTS, my AGS balance is here:
http://www1.agsexplorer.com/balances/152nRpBkqiFpa6YTG63Z4AnjUfM9y9jCwx

I own 1338.6988 PTS, i bought these before 15 july 2014.

Should i be in that list?

If so, which address should i use to look in the list if i am there?

Regards, DJ
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: 麥可貓 on September 30, 2014, 10:46:56 am
I got a problem that all my 'recieve addresses' have 189.3689 PTS checked by coinplorer.com.
but actually my wallet balance is 339.96378357 PTS right now and at the snapshop date.

so which number should I expect?
117600000000 * 189.3689
or
117600000000 * 339.96378357

thank you
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: deejay on September 30, 2014, 12:11:20 pm
ahh, i got it

both are in there, thanks


I dont' really understand this post. Is this json on githubusercontent containing the future coin distribution for the DNS project?

I own AGS and PTS, my AGS balance is here:
http://www1.agsexplorer.com/balances/152nRpBkqiFpa6YTG63Z4AnjUfM9y9jCwx

I own 1338.6988 PTS, i bought these before 15 july 2014.

Should i be in that list?

If so, which address should i use to look in the list if i am there?

Regards, DJ
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 30, 2014, 03:13:24 pm
I got a problem that all my 'recieve addresses' have 189.3689 PTS checked by coinplorer.com.
but actually my wallet balance is 339.96378357 PTS right now and at the snapshop date.

so which number should I expect?
117600000000 * 189.3689
or
117600000000 * 339.96378357

thank you

PM all relevant addresses and I'll check it out
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: digenido on September 30, 2014, 06:42:24 pm
I have 2094 ags ,but I just  got 47140785664320 DNS. (Pe4o564GFQNqDHXvWVjkspZzCpXaWPYpkR)  Could you help  me check it ?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 30, 2014, 07:17:12 pm
I got a problem that all my 'recieve addresses' have 189.3689 PTS checked by coinplorer.com.
but actually my wallet balance is 339.96378357 PTS right now and at the snapshop date.

so which number should I expect?
117600000000 * 189.3689
or
117600000000 * 339.96378357

thank you

PM all relevant addresses and I'll check it out

Looks like this was a change address issue
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 30, 2014, 07:32:28 pm
I have 2094 ags ,but I just  got 47140785664320 DNS. (Pe4o564GFQNqDHXvWVjkspZzCpXaWPYpkR)  Could you help  me check it ?

I looked at the listaddressgroupings you sent and all the keys are there. Your balance is 2094402.1839 DNS
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: bitder on September 30, 2014, 09:01:43 pm
If the genesis supply is 5 Billion then AGS accounts for 1 Billion (or 20%). Does this mean AGS/PTS is already pre-diluted according to the *Final, guaranteed allocation* thread?

https://bitsharestalk.org/index.php?topic=6753.msg89570#msg89570

Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 30, 2014, 09:04:22 pm
If the genesis supply is 5 Billion then AGS accounts for 1 Billion (or 20%). Does this mean AGS/PTS is already pre-diluted according to the *Final, guaranteed allocation* thread?

https://bitsharestalk.org/index.php?topic=6753.msg89570#msg89570

AGS gets 2 billion or 40% of the initial allocation (at least 20% of theoretical possible max 10bn)
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: bitder on September 30, 2014, 09:14:58 pm
If the genesis supply is 5 Billion then AGS accounts for 1 Billion (or 20%). Does this mean AGS/PTS is already pre-diluted according to the *Final, guaranteed allocation* thread?

https://bitsharestalk.org/index.php?topic=6753.msg89570#msg89570

AGS gets 2 billion or 40% of the initial allocation (at least 20% of theoretical possible max 10bn)
That's what I thought. Then I think we have a problem with the genesis file.
I scaled the genesis_keyid.json by 1e-8 (which gives me a total supply of 5 billion)
I checked one of my AGS addresses and it was essentially scaling the AGS balance by 1000 (i.e. from a total of 1 Million AGS to 1 Billion DNS)
This means that AGS is only 20% of the total genesis supply.
(Can someone else verify with their AGS addresses?)
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 30, 2014, 09:16:38 pm
If the genesis supply is 5 Billion then AGS accounts for 1 Billion (or 20%). Does this mean AGS/PTS is already pre-diluted according to the *Final, guaranteed allocation* thread?

https://bitsharestalk.org/index.php?topic=6753.msg89570#msg89570

AGS gets 2 billion or 40% of the initial allocation (at least 20% of theoretical possible max 10bn)
That's what I thought. Then I think we have a problem with the genesis file.
I scaled the genesis_keyid.json by 1e-8 (which gives me a total supply of 5 billion)
I checked one of my AGS addresses and it was essentially scaling the AGS balance by 1000 (i.e. from a total of 1 Million AGS to 1 Billion DNS)
This means that AGS is only 20% of the total genesis supply.
(Can someone else verify with their AGS addresses?)

There's 2 million AGS total. So 2mn * 1k = 2bn, or 40% of the initial supply.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: bitder on September 30, 2014, 09:19:38 pm
If the genesis supply is 5 Billion then AGS accounts for 1 Billion (or 20%). Does this mean AGS/PTS is already pre-diluted according to the *Final, guaranteed allocation* thread?

https://bitsharestalk.org/index.php?topic=6753.msg89570#msg89570

AGS gets 2 billion or 40% of the initial allocation (at least 20% of theoretical possible max 10bn)
That's what I thought. Then I think we have a problem with the genesis file.
I scaled the genesis_keyid.json by 1e-8 (which gives me a total supply of 5 billion)
I checked one of my AGS addresses and it was essentially scaling the AGS balance by 1000 (i.e. from a total of 1 Million AGS to 1 Billion DNS)
This means that AGS is only 20% of the total genesis supply.
(Can someone else verify with their AGS addresses?)

There's 2 million AGS total. So 2mn * 1k = 2bn, or 40% of the initial supply.
Thanks, forgot there was 1 million AGS for PTS donations and 1 million AGS for BTC donations.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: margie on September 30, 2014, 11:13:45 pm
Hello, there were about 307 PTS in this address "PXxj9SJYTQyBMbbQYwYjyhwA1igya8XsDy" before Aug 21, but it only received 245089 DNS.
Could you help me? Thank you.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on September 30, 2014, 11:17:02 pm
Hello, there are about 307 PTS in this address "PXxj9SJYTQyBMbbQYwYjyhwA1igya8XsDy" before Aug 21, but it only received 245089 DNS.
Could you help me? Thank you.

Type "listaddressgroupings" in the console (help -> debug window) and paste the results here:  http://bitbalance.azurewebsites.net/
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: margie on October 01, 2014, 12:08:53 am
Hello, there are about 307 PTS in this address "PXxj9SJYTQyBMbbQYwYjyhwA1igya8XsDy" before Aug 21, but it only received 245089 DNS.
Could you help me? Thank you.

Type "listaddressgroupings" in the console (help -> debug window) and paste the results here:  http://bitbalance.azurewebsites.net/

I forgot other addresses :-[ . I'm so sorry and thanks a lot.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: 麥可貓 on October 01, 2014, 11:32:36 am
I got a problem that all my 'recieve addresses' have 189.3689 PTS checked by coinplorer.com.
but actually my wallet balance is 339.96378357 PTS right now and at the snapshop date.

so which number should I expect?
117600000000 * 189.3689
or
117600000000 * 339.96378357

thank you

PM all relevant addresses and I'll check it out

I found the rest addresses, thank you very much!
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: Harvey on October 02, 2014, 03:05:39 am
As listed in http://bitbalance.azurewebsites.net/, the amounts of DNS are correct for my pts/btc wallets.  +5%
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: unsoindovo on October 02, 2014, 06:49:41 am
hy everyone!
i'm trying to check my balance on http://bitbalance.azurewebsites.net/.
I'm not able to check with my PTS address.
on the bottom text box i read "PTS - List address groupings" but in the example i read "angel Share.
Example: [ [ "PaNGELA9axAjyAabZi79NftqLi7Duvt9jX", 0, "Angel shares" ], ] ]
what is the correct sintax to submit?

thanks!
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on October 02, 2014, 06:52:39 am
hy everyone!
i'm trying to check my balance on http://bitbalance.azurewebsites.net/.
I'm not able to check with my PTS address.
on the bottom text box i read "PTS - List address groupings" but in the example i read "angel Share.
Example: [ [ "PaNGELA9axAjyAabZi79NftqLi7Duvt9jX", 0, "Angel shares" ], ] ]
what is the correct sintax to submit?

thanks!
you open up your bitshares-PTS wallet .. go to the debug window and type "listaddressgroupings" .. the returning lines you can paste into the SECOND input form of the webpage ... tada ...
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: cike on October 02, 2014, 08:24:07 am
PjsRLuzoci2NqPwfT748raPTvYxJ2EG93x  AGS :126.13827015
DNS;  11566056434000
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: callmeluc on October 02, 2014, 09:19:21 am
Check this please:

PigwTMuqg8CknH6qFu6mymiSECwKQ6ZTJx   61.33245366 AGS,  DNS 0
PmWQYMb9NyfEpRRXKNp9YmzrMB1cKZyrGn   63.05502769 AGS, DNS 0
Pd2HjeZ4WkMbu9fqiyhk3pjrf6HMGpgLqN        61.33245366 AGS, DNS 0
Pe4kbST4aivJ6q78sayJvhx8kxrzKnRrN4          61.93773607 AGS,  DNS 0


thanks.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: sudo on October 02, 2014, 09:44:40 am
 :'( :'(  OMG  it there  any  tools  to  check the balance  easily?
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: xeroc on October 02, 2014, 09:47:48 am
:'( :'(  OMG  it there  any  tools  to  check the balance  easily?
https://bitsharestalk.org/index.php?topic=9380.msg123880#msg123880
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on October 02, 2014, 02:21:17 pm
PjsRLuzoci2NqPwfT748raPTvYxJ2EG93x  AGS :126.13827015
DNS;  11566056434000

Click "separate view" on AGS explorer to see breakdown by address. You have another key related to this with the rest.


Check this please:

PigwTMuqg8CknH6qFu6mymiSECwKQ6ZTJx   61.33245366 AGS,  DNS 0
PmWQYMb9NyfEpRRXKNp9YmzrMB1cKZyrGn   63.05502769 AGS, DNS 0
Pd2HjeZ4WkMbu9fqiyhk3pjrf6HMGpgLqN        61.33245366 AGS, DNS 0
Pe4kbST4aivJ6q78sayJvhx8kxrzKnRrN4          61.93773607 AGS,  DNS 0


thanks.

AGSexplorer says the first one's AGS is credited here:  http://www1.agsexplorer.com/balances/PigwTMuqg8CknH6qFu6mymiSECwKQ6ZTJx?view=merged
This address is present with the correct amount for your first one:  PkgT89Z3o9oMf2FuyFaqhwW2QHhDeHFxVv

Code: [Select]
        [
            "PkgT89Z3o9oMf2FuyFaqhwW2QHhDeHFxVv",
            6133245366000
        ],


I think you have AGS in different addresses than you think. Check your change addresses.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: sudo on October 02, 2014, 02:58:22 pm
:'( :'(  OMG  it there  any  tools  to  check the balance  easily?
https://bitsharestalk.org/index.php?topic=9380.msg123880#msg123880


 +5% +5% awesome tools
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: unsoindovo on October 03, 2014, 06:22:00 am
I know i' m not in the right thread but
Theare similar tool for bitshare VOTE?

Thanks!
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: willaim on October 03, 2014, 09:48:08 pm
@toast, I am sure that you forgot to replace wrong PTS address with these substitutions:
https://bitsharestalk.org/index.php?topic=4748.15

thank BM for your confirmation! thank god that PTS exchange trader has given me the signature for my local PTS address.

Address: PikAq7jB7yHJnZ8gsBXFLWquD1bPoeP7x5
Message: New PTS Address is PjjYtWpwmwEMA1MK9mjpDpSYzkTMPgjm7X
Signature: IEe5mmZs9q9kjhYVmhqW3RYvPJ8kbe9q3HqwL8hX9FoCN0XxzHPo3t1Fb1Lput/SQ1UaNwxSKzO7K9fjJ6yUVdw=

could you check the message signature then update the genesis blcok with my replaced PTS in the next DNS version?

I will use these substitutions after I check signatures:

https://bitsharestalk.org/index.php?topic=4748.0
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: Tuck Fheman on October 07, 2014, 03:38:44 am
*Sorry if this is the wrong place, but it looks like the right place to bring this up.

I donated to AGS via Multibit wallet in April.

I confirmed my address and amount at http://bitshares.org/dns_genesis_ags_pts.txt - http://www1.agsexplorer.com/balances and http://bitbalance.azurewebsites.net.

However, when I try to import my wallet/keys into KeyID from Multibit, it says all went fine, but no DNS are added and it should be around 25,720 according to all three websites.

Also note that the message displayed says, "Keys from Bitcoin/PTS wallet were successfully imported", despite selecting Multibit.

Edit : I'm only having problems with the Multibit import for my AGS purchase via bitcoin. My PTS wallet imported without issues.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: hadrian on October 07, 2014, 07:01:06 pm
By the way, I believe the problem I mentioned on page 2 of this topic is resolved by this (thanks pc) https://bitsharestalk.org/index.php?topic=9760.msg126795#msg126795 (https://bitsharestalk.org/index.php?topic=9760.msg126795#msg126795)

Toast said:

Sounds like a bounty.. Who wants to recreate the snapshot?

There are several DACs coming up soon, I feel like we at least need an "official" AGS distribution

Referring to:

Something's not right with address 14fXr2UTa17CadcZ911N7TBFqMLpqsfNae

The same problem arose with Lottoshares here: https://bitsharestalk.org/index.php?topic=4879.msg64977#msg64977 (https://bitsharestalk.org/index.php?topic=4879.msg64977#msg64977)

AGS Explorer shows 566.53948028 AGS
Your number for this address is 56596237510000

The numbers aren't THAT far out, but other addresses don't seem to have this problem.
I'm curious as to the cause of the discrepancy...

Is it bad form to quote myself? Dunno...

Anyway, is there an explanation for the discrepancy for address 14fXr2UTa17CadcZ911N7TBFqMLpqsfNae?

The figures on AGSexplorer don't seem to match those reported for the genesis blocks.

It's happened with LottoShares and DNS. Will it occur with all DACs? It bothers me because I don't understand it...
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: Tuck Fheman on October 08, 2014, 07:38:51 pm
I'm assuming this is time sensitive (from the title) so I'm going to bump this ...  http://www1.agsexplorer.com/balances/1kBDPTUphPdpYrbyw9pVs4i6EzsTPfJk4 (http://www1.agsexplorer.com/balances/1kBDPTUphPdpYrbyw9pVs4i6EzsTPfJk4)

I did not receive the 25,720.xxx DNS from this AGS donation via Bitcoin from a Multibit wallet. See above for more details.
Title: Re: [DNS] ** LAST CHANCE TO CHECK ALLOCATION **
Post by: toast on October 08, 2014, 07:43:10 pm
Locking this because the DAC has launched already.
If your problem isn't addressed by this fix, it means you're probably not importing your keys properly:  https://bitsharestalk.org/index.php?topic=9760.msg126795#msg126795