NA

[julian071]

Am I the only one getting a cloudflare SSL error at community.gulden.com?   developer.gulden.com and www.gulden.com working fine.

Error 526 Ray ID: 2318d36da570220a • 2015-10-07 10:12:19 UTC
Invalid SSL certificate

Also fine here. Is the time and date of your computer off?

[veertje]

I love the big Backup-button in the new wallet! Overall design is also much better!

I have a technical question about backing up your wallet. Today I read in a thread here on Bitcointalk that the Bitcoin Core wallet works in a way, that when you send BTC, your existing backup of your wallet.dat essentially becomes worthless. See here: https://bitcointalk.org/index.php?topic=359.0

Does the Guldencoin wallet work the same way?

The example was a post of 2010. After that a solution has been added as it seems for this. So it is ok now, if i am correct.
I have replaced some wallet.dat in the past and never got troubles, but maybe MaNI can tell us more about this?

..... the keypool feature did not exist yet at the time. This thread was created in July 14, 2010, while the keypool feature was first added to the bitcoin qt by satoshi in October 09, 2010. https://bitcointalk.org/index.php?topic=1414.0.

[MaNI]

I love the big Backup-button in the new wallet! Overall design is also much better!
I have a technical question about backing up your wallet. Today I read in a thread here on Bitcointalk that the Bitcoin Core wallet works in a way, that when you send BTC, your existing backup of your wallet.dat essentially becomes worthless. See here: https://bitcointalk.org/index.php?topic=359.0

It is a bit more complicated than this. (The backups are not worthless from a single send but they can be worthless if you don't do them frequently enough)

All (bitcoin-qt based) wallets work as follows regarding addresses:
1) Addresses are allocated 100 at a time and kept in a pool.
2) As new addresses are needed they are taken from the pool.
3) When the pool is exhausted a further 100 addresses are allocated.

So when you save a backup, you are backing up your currently used addresses along with (~100) future addresses, once you create more than 100 new addresses you have reached a point where you are using addresses that are not in your backup, at this point your backup is no longer safe, any coins in the new addresses will be lost if you restore from backup.

The big caveat here is that every single time you send coins to a new change address is made and all the money from the sending address goes into this change address, so thats 1 address from the pool used for every send, so you want to backup every 100 transactions ideally..

Things you can do here to protect yourself further:
1) Set a larger pool size in your Gulden.conf:
keypool=5000 (for instance), your backups are then good for a longer period of time.
2) Use coin control and set a fixed change address (be aware that this undermines your secrecy somewhat..) - you won't use a new address for every send transaction then.

Does the Guldencoin wallet work the same way?

Yes, though this is probably something we will look into in future.

[Jero]

And a nice development overview it is!

https://developer.gulden.com/

LOVE IT!

[veertje]

Thanks MaNI for explaining. Also store private keys of the addresses as a backup is an option. Maybe an option to add in the wallet as well later on maybe?

Great new wallet by the way  

[julian071]

Thank you MaNI!

[Frais]

Am I the only one getting a cloudflare SSL error at community.gulden.com?   developer.gulden.com and www.gulden.com working fine.

Error 526 Ray ID: 2318d36da570220a • 2015-10-07 10:12:19 UTC
Invalid SSL certificate

No, I also get a SSL error when I visit the forum, only on mobile (Blackberry) though. The only thing I can think of when I check the source code that there're several http:// links on the page that might trigger it.

[WaterLooDown]

And a nice development overview it is!

https://developer.gulden.com/

LOVE IT!

All the credit goes to Rijk for setting that new website up. I even have my own blog page which I will use for future development updates.

[markanth]

Am I the only one getting a cloudflare SSL error at community.gulden.com?   developer.gulden.com and www.gulden.com working fine.

Error 526 Ray ID: 2318d36da570220a • 2015-10-07 10:12:19 UTC
Invalid SSL certificate

No, I also get a SSL error when I visit the forum, only on mobile (Blackberry) though. The only thing I can think of when I check the source code that there're several http:// links on the page that might trigger it.

I get the ssl error on android 5 (chrome), windows 7 (IE and chrome), and blackberry 10

[GeorgeAurea]

I love the big Backup-button in the new wallet! Overall design is also much better!
I have a technical question about backing up your wallet. Today I read in a thread here on Bitcointalk that the Bitcoin Core wallet works in a way, that when you send BTC, your existing backup of your wallet.dat essentially becomes worthless. See here: https://bitcointalk.org/index.php?topic=359.0

It is a bit more complicated than this. (The backups are not worthless from a single send but they can be worthless if you don't do them frequently enough)

All (bitcoin-qt based) wallets work as follows regarding addresses:
1) Addresses are allocated 100 at a time and kept in a pool.
2) As new addresses are needed they are taken from the pool.
3) When the pool is exhausted a further 100 addresses are allocated.

So when you save a backup, you are backing up your currently used addresses along with (~100) future addresses, once you create more than 100 new addresses you have reached a point where you are using addresses that are not in your backup, at this point your backup is no longer safe, any coins in the new addresses will be lost if you restore from backup.

The big caveat here is that every single time you send coins to a new change address is made and all the money from the sending address goes into this change address, so thats 1 address from the pool used for every send, so you want to backup every 100 transactions ideally..

Things you can do here to protect yourself further:
1) Set a larger pool size in your Gulden.conf:
keypool=5000 (for instance), your backups are then good for a longer period of time.
2) Use coin control and set a fixed change address (be aware that this undermines your secrecy somewhat..) - you won't use a new address for every send transaction then.

Does the Guldencoin wallet work the same way?

Yes, though this is probably something we will look into in future.

So, not using too many different addresses, would add up in existing backups being still valid over longer periods of time?

[veertje]

Because of new page: wallet 1.5.1 available at https://developer.gulden.com/apps

1.5.1 is now available at our developer site: https://developer.gulden.com/apps

There are some great features   Even a search bar to look after transactions. Transactions can also be sorted out in time and other parameters.










Nice wallet Great job!
All transactions can now be sorted out, that is very good. No syncing indicator anymore also.
A lot of different languages also i see, to choose from.

All in all great step forward, I like it.  Great dev team Gulden has

[WaterLooDown]

Development update:

Prelude:

The initial goal for 1.5.1 was only going to be sorting out bug fixes that came across with the 0.10/0.11 code base update.
A few weeks later it became a larger more in depth project due to the name change to Gulden and other concerns.

The below tasks were achieved for 1.5.1

1. Renaming to Gulden.
A lot more effort goes into a name change then what's on the surface especially on the building process of the wallet. QR codes with Gulden wallet will scan for old Guldencoin addresses and new
Gulden addresses so that all addresses are catered for going forward. The new android wallet update also includes both.

The install process also caters for moving the wallet.dat file into the new location so you don't have to do this manually. This was very important to implement for new users to Gulden and crypto.

2. UI update.
We felt it was important to put a unique touch on 1.5.1 to showcase the direction we moving. The UI changes and rebranding along with the removal of the overview screen and the addition of the backup tab felt like a good first move. The backup wallet button is not visible in normal wallets and as the saying goes "out of sight out of mind".

The progress bar is another added touch, instead of displaying a count down in time for the sync which would scare most users away a progress bar will now be visible during the sync process.

1.5.1 is the first changes we going to be making to the UI, we expect to have another release before the end of the year.

3. Bug fixes.

The 2 main fixes were:

The max fee(size) has been increased to cater for addresses where a lot of transactions (mainly mining) made up the balance of a particular wallet increasing the size of transactions being sent from that address.
KGW fix for linux 32bit builds.

4. Streamlining of the build process
MaNI has does a incredible job with our build server, a lot of the time for 1.5.1 was spent perfecting the process of delivering new wallet builds whenever we make changes and want to test or release. This is going to save us a lot of time in the future and we can start focusing on more functionality.

The above was a great team effort from the core developers to web design to testing.



1.5.1 is now available at our developer site: https://developer.gulden.com/apps

[MaNI]

I love the big Backup-button in the new wallet! Overall design is also much better!
I have a technical question about backing up your wallet. Today I read in a thread here on Bitcointalk that the Bitcoin Core wallet works in a way, that when you send BTC, your existing backup of your wallet.dat essentially becomes worthless. See here: https://bitcointalk.org/index.php?topic=359.0

It is a bit more complicated than this. (The backups are not worthless from a single send but they can be worthless if you don't do them frequently enough)

All (bitcoin-qt based) wallets work as follows regarding addresses:
1) Addresses are allocated 100 at a time and kept in a pool.
2) As new addresses are needed they are taken from the pool.
3) When the pool is exhausted a further 100 addresses are allocated.

So when you save a backup, you are backing up your currently used addresses along with (~100) future addresses, once you create more than 100 new addresses you have reached a point where you are using addresses that are not in your backup, at this point your backup is no longer safe, any coins in the new addresses will be lost if you restore from backup.

The big caveat here is that every single time you send coins to a new change address is made and all the money from the sending address goes into this change address, so thats 1 address from the pool used for every send, so you want to backup every 100 transactions ideally..

Things you can do here to protect yourself further:
1) Set a larger pool size in your Gulden.conf:
keypool=5000 (for instance), your backups are then good for a longer period of time.
2) Use coin control and set a fixed change address (be aware that this undermines your secrecy somewhat..) - you won't use a new address for every send transaction then.

Does the Guldencoin wallet work the same way?

Yes, though this is probably something we will look into in future.

So, not using too many different addresses, would add up in existing backups being still valid over longer periods of time?

Yes, basically.
Except keep in mind that every time you send coins a new address is created - when using the default setup - not just when you create new receiving addresses.
If you only do one transaction a month then your backups are good for many years, if you send frequently you need to backup more frequently, or look at some of the other options I mentioned like a larger pool.

[WaterLooDown]

All future development updates will be posted to:

https://developer.gulden.com/blog/

I have updated the blog to also include the new android wallet that was released on the 1st October.

Development update:

Prelude:

The initial goal for 1.5.1 was only going to be sorting out bug fixes that came across with the 0.10/0.11 code base update.
A few weeks later it became a larger more in depth project due to the name change to Gulden and other concerns.

The below tasks were achieved for 1.5.1

1. Renaming to Gulden.
A lot more effort goes into a name change then what's on the surface especially on the building process of the wallet. QR codes with Gulden wallet will scan for old Guldencoin addresses and new
Gulden addresses so that all addresses are catered for going forward. The new android wallet update also includes both.

The install process also caters for moving the wallet.dat file into the new location so you don't have to do this manually. This was very important to implement for new users to Gulden and crypto.

2. UI update.
We felt it was important to put a unique touch on 1.5.1 to showcase the direction we moving. The UI changes and rebranding along with the removal of the overview screen and the addition of the backup tab felt like a good first move. The backup wallet button is not visible in normal wallets and as the saying goes "out of sight out of mind".

The progress bar is another added touch, instead of displaying a count down in time for the sync which would scare most users away a progress bar will now be visible during the sync process.

1.5.1 is the first changes we going to be making to the UI, we expect to have another release before the end of the year.

3. Bug fixes.

The 2 main fixes were:

The max fee(size) have been increased to cater for addresses where a lot of transactions (mainly mining) made up the balance of a particular wallet increasing the size of transactions being sent from that address.
KGW fix for linux 32bit builds.

4. Streamlining of the build process
MaNI has does a incredible job with our build server, a lot of the time for 1.5.1 was spent perfecting the process of delivering new wallet builds whenever we make changes and want to test or release. This is going to save us a lot of time in the future and we can start focusing on more functionality.

The above was a great team effort from the core developers to web design to testing.



1.5.1 is now available at our developer site: https://developer.gulden.com/apps

[veertje]

@ Waterloo, don't forget to update the https://timeline.gulden.com/ as well

[WaterLooDown]

@ Waterloo, don't forget to update the https://timeline.gulden.com/ as well

Will sort this out in a bit. It is on my ToDo list for today but thanks for the reminder.

[Jero]

I installed the new Gulden Android app. It ended up with an empty wallet... 

What is the best way to handle this???

[WaterLooDown]

I installed the new Gulden Android app. It ended up with an empty wallet...  

What is the best way to handle this???

You can just do a transfer from the old guldencoin wallet to the new one. I did this aswell, unfortunately the android update didn't include copying over the old private keys automatically like we did for the 1.5.1 wallets.

We also don't expect to do another name change ever again.  

Let us know if you have any issues, both wallets will still work but the new wallet will be more secure.

[Jero]

I installed the new Gulden Android app. It ended up with an empty wallet...  

What is the best way to handle this???

You can just do a transfer from the old guldencoin wallet to the new one. I did this aswell, unfortunately the android update didn't include copying over the old private keys automatically like we did for the 1.5.1 wallets.

We also don't expect to do another name change ever again.  

Let us know if you have any issues, both wallets will still work but the new wallet will be more secure.

I just inported the private keys in the new wallet, it's syncing now (15 months behind). We'll see where it ends up 

[mainpmf]

I installed the new Gulden Android app. It ended up with an empty wallet...  

What is the best way to handle this???

You can just do a transfer from the old guldencoin wallet to the new one. I did this aswell, unfortunately the android update didn't include copying over the old private keys automatically like we did for the 1.5.1 wallets.

We also don't expect to do another name change ever again.  

Let us know if you have any issues, both wallets will still work but the new wallet will be more secure.

I just inported the private keys in the new wallet, it's syncing now (15 months behind). We'll see where it ends up  

I also had a similar issue, I installed the 1.5.1 from scratch on Mac (no appdata gulden folder). My balance wen't to 0 NLG's, when its finished syncing the balance will re-appear? I can see all my previous transactions though, but no balance.