Topic: NA - page 562. (Read 893616 times)

I bet for Germany yesterday no loot received

That is great Shadowmoon, thanks for the update!

To trigger some additional bets today on http://nlgcup.com I placed 5,000 NLG on a Unites States win over Belgium, and 5,000 NLG on a Swiss win over Argentina      

...and for coming Friday 10,000 NLG on a Colombia win over Brasil,
...and for Saturday 10,000 NLG on a Costa Rica win over The Netherlands   

I do want to share some funny experience... This morning at the same time I did a withdrawal both BTC and NLG. NLG was transfered from Coinext to Bittrex in 4 mins including the delay exchanges normally have. BTC is still pending after more than an hour and a half!

Hi Guys,

The importance of this project cannot be underestimated, it will bring a lot of good for NLG. Find out from friends or family if they know anyone that could potentially help out here.

Thanks

Is the team already lobbying for some (big) sponsors to get a budget for a marketing campain or development costs? That could be inside the cryptoland, but outside cryptoland as well. There is a budget reserved in NLG, but maybe get some sponsors in Euro's, to speed up that proces. I think the sponsors can get banners on the many guldencoin websites for their promotion. F.e. on http://www.guldencoinweb.nl and https://guldencoin.com ofcourse.

Thanks for the update ths.

To anyone who is trading at Coinnext, https://coinnext.com this exchange is going to shut down by the 24th of July. So withdraw your funds over there.

Because most used is the most secure? Ask microsoft if that is true.


OpenSSL anyone?

The point that GeertJohan wants to make is that security comes at many levels, you have to secure ALL of them. Webservers are very difficult (and expensive) to secure properly. Security is as strong as the weakest link. Riskmanagement comes second, how much is lost when security is breached? That is way more on a centralized server than on an individual wallet.

Guldencoin has established partnership with Bitscoinshop (http://www.bitscoinshop.com.br/en/) where you can buy items by using Guldencoin, and enjoy 10% discount. As Guldencoin is not yet integrated with the payment platform, you will need to use the following procedure during checkout:
 
1. Customers wishing to purchase using Guldencoin should choose the product, along with signing up with the details and place of delivery;
 
2. Choose the bank transfer as the payment method, meanwhile leave a message to indicate that you want to pay with Guldencoin;
 
3. In the message, specify the dollar amount of your purchase (with 10% discount) and the quote of the current exchanging rate. Bitscoinshop will convert the amount of your purchase into Guldencoin, and send wallet address for payment.
 
4. Once confirmed the payment, items will be delivered.

Buy various mining products, Asics, Gridseed, shoes and dressing. All with 6-month warranty against manufacturing defects!
We have several offers and products please visit our store.

http://www.guldencoinforum.com is down at the moment

GeertJohan I think this can be done secure look at blockchain.info this is probably the most used bitcoin wallet.

They also have alot of open source code at github that you can review.

I have made a post in the hive wallet link, please feel free to make our voices heard.

https://bitcointalk.org/index.php?topic=637227.new#new

In my opinion, an HTML wallets are a tricky business.
First of all, asuming the wallet is served from a webserver: one needs to trust CA's. After diginotar's failure, this is a bit of an issue.
Then there's the problem with javascript, which was never really designed to do crypto stuff. Most default javascript random number generators aren't very good. Furthermore, javascript doesn't exactly run in a safe environment. Code injection is trivial and a simple virus (Aw3some toolbar gadget mp3 downloader v6-plus DOWNLOAD NOW!) could do it. After that there's the subject of 'where do we store the coins aka private keys?'. Either on the server, making the server a huge target. Or in the client? (cookies? local storage? hmm.. I dont know if thats really that great..)..

So. I believe html/js wallets (or wallet front-ends) are definitely very interesting, but I doubt if they should be used in production already.
Browsers are constantly improving and working on security. I think there will come a time that something like this is possible in a safe way.
I'll take a better look at Hive and see how they approached these problems. Maybe they've got some great solutions!

What do we require for iOS?
(I'm not an Objective-C coder, so I might get terminology wrong.)
What we need is an Objective-C library that, on itself, is a complete working guldencoin node implementation with wallet functionality (including persistence).
Possibly this can be achieved by taking Breadwallet and adding scrypt+KGW.
The library should come with unit tests and regression tests.
If the library is forked (for instance from breadwallet), then upstream remote's should still work (keep git history). That way we can merge in new features and improvements.
The library must expose API's to do all the common tasks as seen in the android wallet and guldencoin-qt.
Please contact us before starting to work on this. We'd like to stay in touch throughout the process and avoid multiple people trying to achieve the same; spilling time by doing the same things twice.

This looks really nice.. It seems that it is basically running bitcoinj on the server side and using HTML to display interface stuff.. nice twist to the standard wallet app.

I would highly recommend the dev team contact the lead dev for the Hive wallet.

In this thread - https://bitcointalksearch.org/topic/which-token-should-hive-support-next-637227 - he is asking for suggestions for the next coin to be supported by the Hive Wallet. Here is a a quote...

Will be interesting to hear the teams take on it, will merchants find this acceptable to use in the meantime?

https://github.com/hivewallet

So that saves 5000 dollars?

That is smart, doesn't matter what device you have then... what about security?

Why not fork a HTML5 wallet like hivewallet? Before building native apps. I think this will be cheaper, faster and for all device's.


https://hivewallet.com/

https://github.com/hivewallet