NA

[WaterLooDown]

Timeline has been updated for December:

https://timeline.guldencoin.com

Well done fuse on the brilliant initiative, the physical coins have been really well received by the community.

[veertje]

Store is down again, as Litepaid is returning a cancelled order status on all new orders, regardless of the real status.  Essentially, I've been manually updating orders on the store side for the last few orders.  I have a support ticket in and I will update everyone as soon as I get it resolved.

We need to start the rally for another payment processor.  Maybe coinpayments.net?  Either I'm a complete idiot with this stuff or it is really difficult to get working consistently.

-Fuse

My last order went well, completed with both the confirmation emails. Seems as after 1 transaction is cancelled or not payed in the timeframe, the problem starts with the next orders? Bug litepaid?

[0btc]

To the miner at http://guldenpool.nl:27100 with address Gdx6V8BsBZ79LMQoNjLQ6Ta9q1hzbVgF5h (I feel like I should know who this is.. and hope you're here to read this), please correct your miners; they're adding postfixes to your username/address, i.e. Gdx6V8BsBZ79LMQoNjLQ6Ta9q1hzbVgF5h.10, .11, etc. Unfortunately p2pool does not parse the username as an address with these postfixes, so instead it acts as if it is a regular worker name, meaning that all the NLG ends up in the 'default account', which is my fee address. Please get in touch as soon as you can!

Though apparently the miners for Gdx6V8BsBZ79LMQoNjLQ6Ta9q1hzbVgF5h are no longer adding postfixes to the username, I still haven't been contacted. Whoever you are, mysterious miner(s), I'm just sending you what my fee address received from block 163466 (Sun Dec  7 15:01:23 CET 2014) till block 165021 (Wed Dec 10 10:44:15 CET 2014). I hope that resolves the matter adequately. (This means you'll also be receiving my hefty 0.5% fee - consider it a gesture of gratitude if you will ).
txid: 77f591806b5ff3e6ce3ad1df2c2f71de1f3693507e23fa562be08f7203f36098

P.S. Fuse, I'll be buying a coin as soon as your shop is back online - can't wait to get one! Awesome job!

[ny2cafuse]

Just an update-

I'm currently working with a couple people to try to get the Litepaid issue figured out.  I will keep the store down tonight so that there is no confusion with orders while I'm asleep.  I'll re-enable the store in the morning(PST) so that people can place orders and I can keep an eye on the issues that may occur.  I will be testing possible solutions tonight in the meantime.

I sincerely apologize for the shaky launch.  Thanks to everyone for your patience while I get everything figured out.

-Fuse


UPDATE:

Sent to both Litepaid and the woocommerce plugin dev, who is also a Gulden fan :

This is definitely an issue with when the webhook is called via the cronjob.

I tested 4 separate transactions to verify.  When the webhook is called after the customer completes payment at Litepaid, the order updates correctly.  When the webhook is called during the checkout process, it cancels the order because it sees the order on Litepaid as being "invoice not paid".

I'm guessing there are two approaches to fixing this.  The first is a long delay between webhook calls.  However, if someone was to checkout right when the cronjob ran, it would cancel the order.

Another option is  to find a way to embed the webhook call in the woocommerce checkout process so that it is called when the customer receives the "thank you for your order" screen.  This screen is shown whether the customer pays or not via litepaid.  I tested both paying and not paying, and woocommerce thinks the order happened and displays this page.  Again, there is a chance that a customer could get a cancelled order if two customers are checking out around the same time.  The "thank you" screen displaying for non-payment orders is an issue as well that will need to be patched at some point.

The third option, if it's even possible, is to implement a countdown in the woocommerce plugin that would cancel the order a set time from when the invoice was created.  Litepaid only gives you 15 minutes to complete a transaction anyway.  Some maybe implement a 17 minute timeout(for safe measure).  So the plugin calls LitePaid, finds the invoice and the time of the invoice, and gives woocommerce 17 minutes before it cancels the order.  Again, not sure if it is possible, but it would be the best way of doing this so that you can just call the webhook all the time, and get immediate results.

If anyone else running a woocommerce webshop with the litepaid plugin, please let me know if you've seen this before.  I'm guessing I can't be the only one this is happening to.

I will update everyone when I hear back from both parties.

-Fuse

[Furio]

I have 25

I ordered yesterday morning, but I didn't recieve any confirmation on my order on my email, is this normal?

Just want to make sure my order went OK, have saved the webpage with the confirmation.

Can you let me know if this is normal?

[HKBvM]

Is it correct that 576000 coins are mined everyday? Seems like...alot. Thats like 2.4BTC worth of coins everyday.

Bit of a dumb question, but I was surprised by the results.

[ArieNLG]

Is it correct that 576000 coins are mined everyday? Seems like...alot. Thats like 2.4BTC worth of coins everyday.

Bit of a dumb question, but I was surprised by the results.

You don't know the story? we are open for raping, as a extra service you can mine only the easy bloks.
But thank god our community (dedicated miners) takes the battle every day against clevermining.

[bram_vnl]

howe can i set a nlg:xxxxxxxx adress to my wallet?

[patrickkivits]

Just an update-

I'm currently working with a couple people to try to get the Litepaid issue figured out.  I will keep the store down tonight so that there is no confusion with orders while I'm asleep.  I'll re-enable the store in the morning(PST) so that people can place orders and I can keep an eye on the issues that may occur.  I will be testing possible solutions tonight in the meantime.

I sincerely apologize for the shaky launch.  Thanks to everyone for your patience while I get everything figured out.

-Fuse


UPDATE:

Sent to both Litepaid and the woocommerce plugin dev, who is also a Gulden fan :

This is definitely an issue with when the webhook is called via the cronjob.

I tested 4 separate transactions to verify.  When the webhook is called after the customer completes payment at Litepaid, the order updates correctly.  When the webhook is called during the checkout process, it cancels the order because it sees the order on Litepaid as being "invoice not paid".

I'm guessing there are two approaches to fixing this.  The first is a long delay between webhook calls.  However, if someone was to checkout right when the cronjob ran, it would cancel the order.

Another option is  to find a way to embed the webhook call in the woocommerce checkout process so that it is called when the customer receives the "thank you for your order" screen.  This screen is shown whether the customer pays or not via litepaid.  I tested both paying and not paying, and woocommerce thinks the order happened and displays this page.  Again, there is a chance that a customer could get a cancelled order if two customers are checking out around the same time.  The "thank you" screen displaying for non-payment orders is an issue as well that will need to be patched at some point.

The third option, if it's even possible, is to implement a countdown in the woocommerce plugin that would cancel the order a set time from when the invoice was created.  Litepaid only gives you 15 minutes to complete a transaction anyway.  Some maybe implement a 17 minute timeout(for safe measure).  So the plugin calls LitePaid, finds the invoice and the time of the invoice, and gives woocommerce 17 minutes before it cancels the order.  Again, not sure if it is possible, but it would be the best way of doing this so that you can just call the webhook all the time, and get immediate results.

If anyone else running a woocommerce webshop with the litepaid plugin, please let me know if you've seen this before.  I'm guessing I can't be the only one this is happening to.

I will update everyone when I hear back from both parties.

-Fuse

I have updated the WooCommerce plugin and added a delay of 17 minutes for automated order status updates (15 minutes to complete Litepaid transaction + 2 minutes buffer)

This will make sure the order status does not get updated before the transaction could be completed in Litepaid.

If anyone is using this plugin please update to 1.1.3, download here: https://github.com/patrickkivits/woocommerce-litepaid.com

Please feel free to contact me if any help is needed!

[24hralttrade]

Patrick Kivits using Guldencoins to get some new jeans

Also having a little chat about mijnwebwinkel.nl for using litepaid/guldencoins.

[/GeertJohan]

Good Morning Guldencoin Community!

I have some great news to share with you. The early release of the diffsim has just been pushed to GitHub.

This version contains a simple hashrate wave simulation and the DGW3 algorithm.
The first things on my TODO list are: larger waves simulation and jump pool simulation.
A graphical user interface might be added later, especially having something to render graphs would be great.

This version is not very user-friendly yet, so expect a bumpy ride.
https://github.com/GeertJohan/diffsim

I welcome contributions to this project very much!

Feedback is welcome here, and in the thread on the official forums: https://forum.guldencoin.com/index.php?topic=707.0

[veertje]

I have updated the WooCommerce plugin and added a delay of 17 minutes for automated order status updates (15 minutes to complete Litepaid transaction + 2 minutes buffer)

This will make sure the order status does not get updated before the transaction could be completed in Litepaid.

If anyone is using this plugin please update to 1.1.3, download here: https://github.com/patrickkivits/woocommerce-litepaid.com

Please feel free to contact me if any help is needed!

That will do the most Only thing to be mentioned to customers buying, is that confirmation of an order is expected within 17 minutes or does it still confirm just after the order is paid?

Is this also solving the issue after that someone cancels an order? It seemed that after that internal processing also gave problems for the next orders. But not sure about that.

So then only this bug has to be fixed:

... the customer receives the "thank you for your order" screen.  This screen is shown whether the customer pays or not via litepaid.  I tested both paying and not paying, and woocommerce thinks the order happened and displays this page.  Again, there is a chance that a customer could get a cancelled order if two customers are checking out around the same time.  The "thank you" screen displaying for non-payment orders is an issue as well that will need to be patched at some point.

Edit: Sent you a PM about an example of mine, while annulating an order in the paymentproces and how it was processed.

[veertje]

Good Morning Guldencoin Community!

I have some great news to share with you. The early release of the diffsim has just been pushed to GitHub.

This version contains a simple hashrate wave simulation and the DGW3 algorithm.
The first things on my TODO list are: larger waves simulation and jump pool simulation.
A graphical user interface might be added later, especially having something to render graphs would be great.

This version is not very user-friendly yet, so expect a bumpy ride.
https://github.com/GeertJohan/diffsim

I welcome contributions to this project very much!

Feedback is welcome here, and in the thread on the official forums: https://forum.guldencoin.com/index.php?topic=707.0

Good it is ready, GJ When translated other algo's in Go, can this be implemented easy? The larger waves and jump pool simulation, takes it a lot of work further more or was this the most intensive work done. I have no idea, just asking what to expect, think most of us have no clue about the time needed to do such work.

I cannot assist, not a programmer, hope others can.

[/GeertJohan]

Good Morning Guldencoin Community!

I have some great news to share with you. The early release of the diffsim has just been pushed to GitHub.

This version contains a simple hashrate wave simulation and the DGW3 algorithm.
The first things on my TODO list are: larger waves simulation and jump pool simulation.
A graphical user interface might be added later, especially having something to render graphs would be great.

This version is not very user-friendly yet, so expect a bumpy ride.
https://github.com/GeertJohan/diffsim

I welcome contributions to this project very much!

Feedback is welcome here, and in the thread on the official forums: https://forum.guldencoin.com/index.php?topic=707.0

Good it is ready, GJ When translated other algo's in Go, can this be implemented easy? The larger waves and jump pool simulation, takes it a lot of work further more or was this the most intensive work done. I have no idea, just asking what to expect, think most of us have no clue about the time needed to do such work.

I cannot assist, not a programmer, hope others can.

What needs to be done now will be easier. Initial work was the hardest part.
I have released already so others might help

[Meije]

Good Morning Guldencoin Community!

I have some great news to share with you. The early release of the diffsim has just been pushed to GitHub.

This version contains a simple hashrate wave simulation and the DGW3 algorithm.
The first things on my TODO list are: larger waves simulation and jump pool simulation.
A graphical user interface might be added later, especially having something to render graphs would be great.

This version is not very user-friendly yet, so expect a bumpy ride.
https://github.com/GeertJohan/diffsim

I welcome contributions to this project very much!

Feedback is welcome here, and in the thread on the official forums: https://forum.guldencoin.com/index.php?topic=707.0

Nice work Geert!

[LTEX]

Just an update-

I'm currently working with a couple people to try to get the Litepaid issue figured out.  I will keep the store down tonight so that there is no confusion with orders while I'm asleep.  I'll re-enable the store in the morning(PST) so that people can place orders and I can keep an eye on the issues that may occur.  I will be testing possible solutions tonight in the meantime.

I sincerely apologize for the shaky launch.  Thanks to everyone for your patience while I get everything figured out.

-Fuse


UPDATE:

Sent to both Litepaid and the woocommerce plugin dev, who is also a Gulden fan :

This is definitely an issue with when the webhook is called via the cronjob.

I tested 4 separate transactions to verify.  When the webhook is called after the customer completes payment at Litepaid, the order updates correctly.  When the webhook is called during the checkout process, it cancels the order because it sees the order on Litepaid as being "invoice not paid".

I'm guessing there are two approaches to fixing this.  The first is a long delay between webhook calls.  However, if someone was to checkout right when the cronjob ran, it would cancel the order.

Another option is  to find a way to embed the webhook call in the woocommerce checkout process so that it is called when the customer receives the "thank you for your order" screen.  This screen is shown whether the customer pays or not via litepaid.  I tested both paying and not paying, and woocommerce thinks the order happened and displays this page.  Again, there is a chance that a customer could get a cancelled order if two customers are checking out around the same time.  The "thank you" screen displaying for non-payment orders is an issue as well that will need to be patched at some point.

The third option, if it's even possible, is to implement a countdown in the woocommerce plugin that would cancel the order a set time from when the invoice was created.  Litepaid only gives you 15 minutes to complete a transaction anyway.  Some maybe implement a 17 minute timeout(for safe measure).  So the plugin calls LitePaid, finds the invoice and the time of the invoice, and gives woocommerce 17 minutes before it cancels the order.  Again, not sure if it is possible, but it would be the best way of doing this so that you can just call the webhook all the time, and get immediate results.

If anyone else running a woocommerce webshop with the litepaid plugin, please let me know if you've seen this before.  I'm guessing I can't be the only one this is happening to.

I will update everyone when I hear back from both parties.

-Fuse

I have WooCommerce as well with LitePaid Plugin. Had Litepaid dev logon to my store and he fixed the issues. His name is Kenny...

[ny2cafuse]

I have WooCommerce as well with LitePaid Plugin. Had Litepaid dev logon to my store and he fixed the issues. His name is Kenny...

I've been in correspondence with Kenny.  I haven't heard back from him yet regarding the info I sent to him and Patrick.  However, Patrick was extremely quick in providing a patch for the issue.  I will be installing the new plugin right now and testing transactions to verify that everything is working.

Do you know what Kenny did to resolve the issue on your site?

I have updated the WooCommerce plugin and added a delay of 17 minutes for automated order status updates (15 minutes to complete Litepaid transaction + 2 minutes buffer)

This will make sure the order status does not get updated before the transaction could be completed in Litepaid.

If anyone is using this plugin please update to 1.1.3, download here: https://github.com/patrickkivits/woocommerce-litepaid.com

Please feel free to contact me if any help is needed!

That will do the most Only thing to be mentioned to customers buying, is that confirmation of an order is expected within 17 minutes or does it still confirm just after the order is paid?

Is this also solving the issue after that someone cancels an order? It seemed that after that internal processing also gave problems for the next orders. But not sure about that.

So then only this bug has to be fixed:

... the customer receives the "thank you for your order" screen.  This screen is shown whether the customer pays or not via litepaid.  I tested both paying and not paying, and woocommerce thinks the order happened and displays this page.  Again, there is a chance that a customer could get a cancelled order if two customers are checking out around the same time.  The "thank you" screen displaying for non-payment orders is an issue as well that will need to be patched at some point.

Edit: Sent you a PM about an example of mine, while annulating an order in the paymentproces and how it was processed.

I'll keep an eye on the transactions today and see if they continue to have issues.  I agree that the non-payment issue will still probably be there, but at least orders won't go cancelled when they aren't supposed to.  That was 90% of my problems before.

I have 25

I ordered yesterday morning, but I didn't recieve any confirmation on my order on my email, is this normal?

Just want to make sure my order went OK, have saved the webpage with the confirmation.

Can you let me know if this is normal?

Furio, your order went through ok.  The issues with processing orders stopped the emails from being sent out, so I will see if I can force the email out again.



Updates to follow, store should be open again in the next hour or so if everything looks good.

-Fuse

[ny2cafuse]

Good Morning Guldencoin Community!

I have some great news to share with you. The early release of the diffsim has just been pushed to GitHub.

This version contains a simple hashrate wave simulation and the DGW3 algorithm.
The first things on my TODO list are: larger waves simulation and jump pool simulation.
A graphical user interface might be added later, especially having something to render graphs would be great.

This version is not very user-friendly yet, so expect a bumpy ride.
https://github.com/GeertJohan/diffsim

I welcome contributions to this project very much!

Feedback is welcome here, and in the thread on the official forums: https://forum.guldencoin.com/index.php?topic=707.0

Kudos to you, /GJ!  If I get some time today to play with it, I'll do some testing.

Hey, Investeerder...

-Fuse

[veertje]

Patrick Kivits using Guldencoins to get some new jeans

Also having a little chat about mijnwebwinkel.nl for using litepaid/guldencoins.

So great to see this!

[investeerder]

Good Morning Guldencoin Community!

I have some great news to share with you. The early release of the diffsim has just been pushed to GitHub.

This version contains a simple hashrate wave simulation and the DGW3 algorithm.
The first things on my TODO list are: larger waves simulation and jump pool simulation.
A graphical user interface might be added later, especially having something to render graphs would be great.

This version is not very user-friendly yet, so expect a bumpy ride.
https://github.com/GeertJohan/diffsim

I welcome contributions to this project very much!

Feedback is welcome here, and in the thread on the official forums: https://forum.guldencoin.com/index.php?topic=707.0

Kudos to you, /GJ!  If I get some time today to play with it, I'll do some testing.

Hey, Investeerder...

-Fuse

As soon as the simulator can be used against the NLG blockchain with multipool swings, LTEX will get his 20 000 as promised. In other words the simulator needs to be in a state where it's used to determine the new algorithm settings.

Well done Geert Johan I am shocked you have a flat release already!