Topic: NA - page 537. (Read 893616 times)
I know you guys are busy with the iOS Community Funding, but I just wanted to show you something...
Absolutely fabulous!
Hello,
I have a question: on the old website, we could see how many Dutsch citizen had claimed their Guldencoin, is this still the case on the new one ? I can't find it anymore.
I have a question: on the old website, we could see how many Dutsch citizen had claimed their Guldencoin, is this still the case on the new one ? I can't find it anymore.
Good question!
Right now 1259 valid claims have been placed. All of those are fulfilled (1.259.000 NLG has been sent).
I hope to find some time soon to upgrade our distribution system with a public page displaying the numbers (and maybe even a nice chart).
A zero too many I suppose?
Whoops! Yes that should be 125.900 NLG ofcourse!
Hello,
I have a question: on the old website, we could see how many Dutsch citizen had claimed their Guldencoin, is this still the case on the new one ? I can't find it anymore.
I have a question: on the old website, we could see how many Dutsch citizen had claimed their Guldencoin, is this still the case on the new one ? I can't find it anymore.
Good question!
Right now 1259 valid claims have been placed. All of those are fulfilled (1.259.000 NLG has been sent).
I hope to find some time soon to upgrade our distribution system with a public page displaying the numbers (and maybe even a nice chart).
A zero too many I suppose?
Hello,
I have a question: on the old website, we could see how many Dutsch citizen had claimed their Guldencoin, is this still the case on the new one ? I can't find it anymore.
I have a question: on the old website, we could see how many Dutsch citizen had claimed their Guldencoin, is this still the case on the new one ? I can't find it anymore.
Good question!
Right now 1259 valid claims have been placed. All of those are fulfilled (1.259.000 NLG has been sent).
I hope to find some time soon to upgrade our distribution system with a public page displaying the numbers (and maybe even a nice chart).
I know you guys are busy with the iOS Community Funding, but I just wanted to show you something...
Oh wow I see this merchant doesn't even accept bitcoin yet?!?! Another one... I am feeling so thrilled inside now!!!
3... 2... 1... GO!
Its now possible to pay with euro by banktransfer, Bitcoin payments will be activated later today.
English: https://guldencoin.com/ios-community-funding
Dutch: https://guldencoin.com/nl/ios-community-funding
Its now possible to pay with euro by banktransfer, Bitcoin payments will be activated later today.
English: https://guldencoin.com/ios-community-funding
Dutch: https://guldencoin.com/nl/ios-community-funding
Now this is how a IPO should be done, please let us know when the BTC one will be available.
hi! technical question.. I've got GuldenCoind compiled and running on linux and am trying to get abe going. I got the scrypt-related fork of abe installed but run into the following error. anyone that has abe running against guldencoin, can you please provide me the proper snippets in abe.conf for the coin? maybe I'm missing something.. error code below:
Exception at 103
Failed to catch up {'blkfile_number': 100000, 'dirname': u'/nlg/.guldencoin', 'chain_id': Decimal('9'), 'id': 4L, 'blkfile_offset': 0}
Traceback (most recent call last):
File "Abe/DataStore.py", line 2422, in catch_up
store.catch_up_dir(dircfg)
File "Abe/DataStore.py", line 2475, in catch_up_dir
store.import_blkdat(dircfg, ds, filename[0])
File "Abe/DataStore.py", line 2599, in import_blkdat
store.import_block(b, chain_ids = chain_ids)
File "Abe/DataStore.py", line 1675, in import_block
raise MerkleRootMismatch(b['hash'], tx_hash_array)
MerkleRootMismatch: Block header Merkle root does not match its transactions. block hash=3ea18e15b6bfd7f4323d2df2f5afcb716a89ffef1520d8bea33e521c070d0000
Thanks!! --Mark
Exception at 103
Failed to catch up {'blkfile_number': 100000, 'dirname': u'/nlg/.guldencoin', 'chain_id': Decimal('9'), 'id': 4L, 'blkfile_offset': 0}
Traceback (most recent call last):
File "Abe/DataStore.py", line 2422, in catch_up
store.catch_up_dir(dircfg)
File "Abe/DataStore.py", line 2475, in catch_up_dir
store.import_blkdat(dircfg, ds, filename[0])
File "Abe/DataStore.py", line 2599, in import_blkdat
store.import_block(b, chain_ids = chain_ids)
File "Abe/DataStore.py", line 1675, in import_block
raise MerkleRootMismatch(b['hash'], tx_hash_array)
MerkleRootMismatch: Block header Merkle root does not match its transactions. block hash=3ea18e15b6bfd7f4323d2df2f5afcb716a89ffef1520d8bea33e521c070d0000
Thanks!! --Mark
Is the IOS wallet going to be open source? If so maybe we could lure some other crypto coin community to buy NLG to help fund this project and later fork the wallet for there one need.
This is actualy a very good point.
C.
I 'll contribute for 130.000 NLG. So 13 packages.
Is the IOS dev not willing to take a part of the payment in NLG? That would be much quicker.
Is the IOS dev not willing to take a part of the payment in NLG? That would be much quicker.
Nope, I believe the iOS dev gave a 50% discount in euro's though. That should be enough for now
I contacted a iOS dev that I know to confirm if this is a good deal and he said it's exceptionally good considering how in demand iOS devs are currently. So great job to the team for sourcing this out and getting someone to do this.
I 'll contribute for 130.000 NLG. So 13 packages.
Is the IOS dev not willing to take a part of the payment in NLG? That would be much quicker.
Is the IOS dev not willing to take a part of the payment in NLG? That would be much quicker.
Nope, I believe the iOS dev gave a 50% discount in euro's though. That should be enough for now
One more question before I contribute.
In the event your dev fails to deliver, can we return the NLG for our BTC back and will the dev give the deposit back in this case?
In the event your dev fails to deliver, can we return the NLG for our BTC back and will the dev give the deposit back in this case?
Good question!
I know this sounds Cliche and it is
but failure is not really a option here. This will be the devs fulltime project for the next 4-6 weeks and along with the team devs and designers they will be working closely together. So this is the devs paycheck for the month. I also personally tried looking for a iOS dev and trust me they are extremely busy these days so we are lucky enough to have a very skilled one that loves cryptos and wants to be involved in making this a success and history for being the first standalone scrypt wallet.In the slight chance the project doesn't succeed we won't let the community down and people will be compensated with difference in market related NLG.
Just to add since this is a community funded project , the team will keep us informed every step of the way with the progress, it won't be like the other projects where we surprise you. We understand total transparency is needed in the development phase of this iOS wallet.
Good answer!!
One more question before I contribute.
In the event your dev fails to deliver, can we return the NLG for our BTC back and will the dev give the deposit back in this case?
In the event your dev fails to deliver, can we return the NLG for our BTC back and will the dev give the deposit back in this case?
Good question!
I know this sounds Cliche and it is
but failure is not really a option here. This will be the devs fulltime project for the next 4-6 weeks and along with the team devs and designers they will be working closely together. So this is the devs paycheck for the month. I also personally tried looking for a iOS dev and trust me they are extremely busy these days so we are lucky enough to have a very skilled one that loves cryptos and wants to be involved in making this a success and history for being the first standalone scrypt wallet.In the slight chance the project doesn't succeed we won't let the community down and people will be compensated with difference in market related NLG.
Just to add since this is a community funded project , the team will keep us informed every step of the way with the progress, it won't be like the other projects where we surprise you. We understand total transparency is needed in the development phase of this iOS wallet.
One more question before I contribute.
In the event your dev fails to deliver, can we return the NLG for our BTC back and will the dev give the deposit back in this case?
In the event your dev fails to deliver, can we return the NLG for our BTC back and will the dev give the deposit back in this case?
Good question!
Please confirm what the final plan for the IPO is, this does mean I won't be buying on the exchanges for the next month as I will be contributing to the iOS wallet. So expect volumes to die out while everyone is giving funds towards this.
400 packages of 10.000 Guldencoin will be sold at 0.017 BTC per package. The original plan as stated here: https://guldencoin.com/guldencoin-ios-community-funding
Thanks
Jump to: