Is it alright if we all PM you our address for shipment already?  |
|
|
|
what the hell, count me in for week 3 as well |
|
|
|
Paid.... Any maybe next draw, people can pick based on address, first come, first served?? Just to change it up. And 3rd draw.....  Just my 2 satoshi. How will these be shipped?? Can they included with the new 2016 coins? This would save an international shipment. And many of the people already have an order in for one!! I think I asked this before, but will there be a cut-off time for payment for that week's coins? At what point does an alternate get to be on the list? Thanks   I am bit confused now, Minerjones you put the adsresses behind the users/numbers.... but isn't it up to Blazed to random assign an address to a number? |
|
|
|
How will the numbers be selected once assigned to an address?? Can we pick or is it assigned based on the list, which is based on time-stamp?? Thanks Well Basically once Blazed has assigned the numbers 1-10 we can just use your list for now. Unless people want specific numbers? What does everyone think about that? Do you mind getting a random number 1-10 based on minerjones list or do you want to pick the numbers yourselves on a 1st come 1st serve basis? I don't mind which number I have/get. Minerjones list is fine by me if everybody agrees on that. |
|
|
|
|
forgot to mention in OP. Payment in BTC only to this address: 1HSSKPNRJ3Y2oAi5w9pG9WmwcwQr7i7tcp
|
|
|
|
I installed Rokos v4 last night on my Pi2 with a Verbatim USB Harddisk and it is very easy to install. Just amazing how easy it is, download img, burn image on SD, insert SD in Pi2, start it up, run raspi-config for some small setting country+keyboard and you are good to go! Previous to the install I copied full blockchain from my linux server on to the USB HDD, then set datadir for bitcoind to the path on the USB HDD, edited bitcoin.conf and you have a full node running. It runs now for about 13 hours and it's very stable. IMAGE Thanks Rokos for making this awesome image, I will donate some BTC soon Remember you can also add: -dbcache=50 to the bitcoin.conf file if you use the system for something else to improve stability. Thanks for your feedback and support! I now entered -dbcache at the bitcoind command line. If I put it in the bitcoin.conf do I also use the - in front of the command or without? which one is right? 1) -dbcache=50 or 2) dbcache=50 |
|
|
|
Holo arrived will start tonight!
They are awesome ! |
|
|
|
I installed Rokos v4 last night on my Pi2 with a Verbatim USB Harddisk and it is very easy to install. Just amazing how easy it is, download img, burn image on SD, insert SD in Pi2, start it up, run raspi-config for some small setting country+keyboard and you are good to go! Previous to the install I copied full blockchain from my linux server on to the USB HDD, then set datadir for bitcoind to the path on the USB HDD, edited bitcoin.conf and you have a full node running. It runs now for about 13 hours and it's very stable.  Thanks Rokos for making this awesome image, I will donate some BTC soon |
|
|
|
I was told never to clean a coin I don't how much coins you have but I want 1 or some more if available, can offer 0.04 BTC like Indianacoin, that's a fair price. |
|
|
|
hmmm... ik loop 1 jaar 42 weken achter  is er ergens een bootstrap.dat te downloaden? of zal ik maar gewoon wachten tot hij gesynced is?gevonden op de developer site |
|
|
|
Je moet de hele checkpoints map verwijderen en dan opnieuw opstarten. Niet alleen de map leegmaken. De app maakt dan een nieuwe map aan en dan zou het goed moeten gaan. Een volgende update wordt dat probleem gefixt.
Ik heb map checkpoints verwijderd, zelfde fout helaas. Ik wacht wel op de update Het kan zijn dat je doordat je zolang niet hebt geüpdate dat er wat meer aan de hand is. In dat geval is het verstandig alles te verwijderen, behalve de wallet.dat file – er in elk geval een backup van hebben/maken. En dan Gulden even opnieuw te installeren (1.5.5 uiteraard  ) en dan je eigen backup/wallet.dat terugzetten. Hij werkt. Ik had alles van guldencoin verwijderd, app 1.5.5 opnieuw geinstalleerd, wallet.dat van backup naar de juiste gekopieerd en alles is nu OK. Ik zie mijn gratis 100 gulden uit 2014 nog netjes in mijn wallet staan  |
|
|
|
Je moet de hele checkpoints map verwijderen en dan opnieuw opstarten. Niet alleen de map leegmaken. De app maakt dan een nieuwe map aan en dan zou het goed moeten gaan. Een volgende update wordt dat probleem gefixt.
Ik heb map checkpoints verwijderd, zelfde fout helaas. Ik wacht wel op de update |
|
|
|
je moet de checkpoint folder leeg maken en dan de wallet opnieuw opstarten
of
Ga > Ga naar map > ~/Library/ Gulden/checkpoints
bekend probleem, volgende update van de wallet word dit opgelost
Checkpoints map leeg gegooid. Op nieuw gulden.app gestart, begon te reindexeren knalde er bij 56% uit. Nogeens herstart, herindex gaat nog goed tot 100% daarna weer zelfde foutmelding. Het lijkt iets met een block(header) die hij niet kan lezen... 2016-01-25 15:33:40 LoadBlockIndexDB(): using synchronized checkpoint 0000000000000000000000000000000000000000000000000000000000000000
2016-01-25 15:33:40 LoadBlockIndexDB(): hashBestChain=e70709347263393ddaae2a962d70e6e8ed2b7ccfe33ba79b0ff520321b45131f height=178442 date=2015-01-03 19:36:53 progress=0.533469
2016-01-25 15:33:40 init message: Verifying blocks...
2016-01-25 15:33:40 Verifying last 288 blocks at level 3
2016-01-25 15:33:40 No coin database inconsistencies in last 289 blocks (529 transactions)
2016-01-25 15:33:40 block index 1866ms
2016-01-25 15:33:40 init message: Loading wallet...
2016-01-25 15:33:41 nFileVersion = 1050500
2016-01-25 15:33:41 Keys: 101 plaintext, 0 encrypted, 0 w/ metadata, 101 total
2016-01-25 15:33:41 wallet 139ms
2016-01-25 15:33:41 ERROR: CheckProofOfWork(): nBits below minimum work
2016-01-25 15:33:41 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=1, nPos=29257186)
2016-01-25 15:33:41 *** Failed to read block
2016-01-25 15:33:43 Shutdown: In progress...
2016-01-25 15:33:43 StopNode()
2016-01-25 15:33:43 Shutdown: done |
|
|
|
Should we have a new sale...?  Or wait until the stock is filling up this week? Or perhaps two sales.... Hmmm.... Ok, let's do this to awaken the thread - sale it is, at least partial:
Until I say stop, the Freecom 2TB USB3 with no external power source will be sold at at 50 US dollar. Of the bought drives, I will include the two 64GB USBs sticks. The one posting in the thread claiming one disk will get one free of charge/shipping until I say stop.
BTW, they are rather nice, very small and handy Just to keep you awake!  I will take the Freecom for $50 with the free stuff and free shipping paid in BTC, I will contact SebastianJu |
|
|
|
Gulden.app start niet op op mijn Mac, OSX 10.11.2 Ik had eerst een oude versie 1.3.0.0, toen heette de map : guldencoin en de app: gulden-qt.app. Nu met versie 1.5.5 is er een nieuwe map: gulden en gulden.app geeft een foutmelding: Error: A fatal internal error occured, see debug.log for details stukje van de debug.log 2016-01-25 10:09:37 Gulden version v1.5.5.0-911f59f-dirty (2015-11-19 04:43:06 -0500)
2016-01-25 10:09:37 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-01-25 10:09:37 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2016-01-25 10:09:37 Default data directory /Users/MYUSERNAME/Library/Application Support/Gulden
2016-01-25 10:09:37 Using data directory /Users/MYUSERNAME/Library/Application Support/Gulden
2016-01-25 10:09:37 Using config file /Users/MYUSERNAME/Library/Application Support/Gulden/Gulden.conf
2016-01-25 10:09:37 Using at most 125 connections (2560 file descriptors available)
2016-01-25 10:09:37 Using 2 threads for script verification
2016-01-25 10:09:37 Using wallet wallet.dat
2016-01-25 10:09:37 init message: Verifying wallet...
2016-01-25 10:09:37 CDBEnv::Open: LogDir=/Users/MYUSERNAME/Library/Application Support/Gulden/database ErrorFile=/Users/MYUSERNAME/Library/Application Support/Gulden/db.log
2016-01-25 10:09:37 Bound to [::]:9231
2016-01-25 10:09:37 Bound to 0.0.0.0:9231
2016-01-25 10:09:37 init message: Loading block index...
2016-01-25 10:09:37 Opening LevelDB in /Users/MYUSERNAME/Library/Application Support/Gulden/blocks/index
2016-01-25 10:09:37 Opened LevelDB successfully
2016-01-25 10:09:37 Opening LevelDB in /Users/MYUSERNAME/Library/Application Support/Gulden/chainstate
2016-01-25 10:09:37 Opened LevelDB successfully
2016-01-25 10:09:39 LoadBlockIndexDB: last block file = 1
2016-01-25 10:09:39 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=36314, size=29393174, heights=142333...178644, time=2014-10-30...2015-01-04)
2016-01-25 10:09:39 Checking all blk files are present...
2016-01-25 10:09:39 LoadBlockIndexDB(): transaction index disabled
2016-01-25 10:09:39 Opening LevelDB in /Users/MYUSERNAME/Library/Application Support/Gulden/checkpoints
2016-01-25 10:09:39 Opened LevelDB successfully
2016-01-25 10:09:39 LoadBlockIndexDB(): using synchronized checkpoint 0000000000000000000000000000000000000000000000000000000000000000
2016-01-25 10:09:39 LoadBlockIndexDB(): hashBestChain=e70709347263393ddaae2a962d70e6e8ed2b7ccfe33ba79b0ff520321b45131f height=178442 date=2015-01-03 19:36:53 progress=0.533704
2016-01-25 10:09:39 init message: Verifying blocks...
2016-01-25 10:09:39 Verifying last 288 blocks at level 3
2016-01-25 10:09:39 No coin database inconsistencies in last 289 blocks (529 transactions)
2016-01-25 10:09:39 block index 2061ms
2016-01-25 10:09:39 init message: Loading wallet...
2016-01-25 10:09:39 nFileVersion = 1050500
2016-01-25 10:09:39 Keys: 101 plaintext, 0 encrypted, 0 w/ metadata, 101 total
2016-01-25 10:09:39 wallet 150ms
2016-01-25 10:09:39 ERROR: CheckProofOfWork(): nBits below minimum work
2016-01-25 10:09:39 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=1, nPos=29257186)
2016-01-25 10:09:39 *** Failed to read block
2016-01-25 10:09:42 Shutdown: In progress...
2016-01-25 10:09:42 StopNode()
2016-01-25 10:09:42 Shutdown: done |
|
|
|
|
Show Posts
