It's ironic that you mention noobs considering the people from the Guldencoin community that have posted here have all been here longer than you.

Your interest in "raping shitcoins" just confirms the true nature of this pool and it's fan-base.  Nice company you keep here, Terk.

-Fuse

No problem, mate.  I'm glad I could help.

I wasn't able to complete the hologram video tonight.  The night just got away from me with the baby.  I will bring a coin to work tomorrow and see if I can't do it there.  I have better camera hardware/software there anyway.  I'm sorry, mate.



PM incoming.

-Fuse

To clarify, I'm not taking it personally.  I just feel with the movement we gained this week to making things work properly, that after 4 months of rallying for it, I can take a step back and refocus.  There are a lot of things that I put on the back burner for months to focus on issues here.  Now that things are moving, I can step back and see how it turns out.

Mind you, if I'm asked to help, I will not deny my help, or my team's.  I am, and they are, still fully committed to this coin's success.

I just feel it's time to take what I learned here and reflect.  If I can apply the knowledge to a future project, it was worth the effort.  Plus I've got a new baby that I'll admit comes second to these long posts sometimes.  I need to stick to the priorities

So happy new year if I don't talk to you all in the next day, and here's to a new year of success!  I'm thinking an anniversary coin maybe?  Who knows.

Cheers,

-Fuse

Each address you generate has a public address and a private key.  The private key is what is used to import the public address into the wallet program.

I would recommend doing this on another computer or using a live linux CD.  You don't want to muck up your main wallet with additional addresses.  Additionally, in terms of security, it's better to do this on a system that can't be comprised.  When you open the wallet, you click on help->console.  In the console you type the following:

importprivkey [the private key] [wallet label]

For instance, this would be an example:

importprivkey 6a7pr11YST2obTrYe7kY2TTURuaQUKBFXwoCbWECBmfmejVDbZT MyCoinWallet

That will add that wallet and allow you to check the funds or spend them.  However, you don't need to load the key into the wallet program to add funds to the wallet.  You can generate an key pair, then send the coins to the public key.  However, I would recommend practicing with generating and adding keys to a wallet first.  One day you'll probably want to be able to pull the coins out or sell them, so you'll want to be able to get to them in the wallet program.  If you ever lose the private key, you can't access the wallet, and those coins will be lost on the chain.

-Fuse

95% of your posts are either about buying games, or they contain the word "shitcoin" or "scamcoin".  You haven't made a single post adding any valuable knowledge to the community as a whole.

It's pretty difficult to sway someone when 95% of your posts are shitposts.

-Fuse

Yes, there were errors in the code I submitted.  There are 2 that I can discern from my talks with /GJ today.  The first was the 25% limit that wasn't a 25% limit.  It was a validation check that acted like a limit on our testnet by rejecting blocks on the confirming nodes.  See /GJ's post about this, although all the a/b/c stuff totally lost me.  The second part to that line of code was that if it was added to the network now, it would have cause the chain to not sync properly on a resync.  Essentially the existing blocks higher than a 25% retarget would have been rejected.  So it is my understanding that the results that were shown with the charts were correct because they were valid with a fresh chain on our testnet.  However, they wouldn't have been valid on the main chain.  Had we worked with the existing blockchain data, we would have identified the error immediately.  My team missed it, and I sincerely apologize for it.

I take full responsibility for these errors.  I knew the code wasn't a final draft.  That is why when Rijk asked me to post the git pull, I asked him to have a few pairs of eyes on the code before we did anything.  It's also why, in light of the simulator timeline /GJ presented, I asked that we test against the simulator.  /GJ is currently working on cleaning up the DIGI code.  I have offered to reach out to the DIGI dev in the meantime.  However, /GJ is confident that he will be able to provide a streamlined DIGI solution, so I am going to stand behind that decision.

I'm going to take a step back from NLG for a little bit.  I just need to refocus on what I'm doing.  I'm not cashing out, and I'm not shutting down the pool.  I will continue to sell physical coins and try to figure out ways to make NLG better outside of the blockchain.  I just feel with the animosity over my involvement, and the movement towards finally fixing the algorithm problems, I don't need to be in the forefront for a while.  I'll continue to follow the thread, but I probably won't push for radical changes like I have in the past.  I'm just going to sit back and watch for a while.

Cheers,

Fuse

We're discussing it now.

-Fuse

I'll work on the video as soon as I get home.

As far as the two-factor key goes, I just mean using any security measure that allows you to not have to store the private key with the wallet address.  That could be a brain wallet mnemonic, or an encrypted key, or even a split key pair(half the key with the coin, and the other half in a secure location).  It's an added level of security to the cold storage options.

Additionally, it looks like cryptolife has changed recently.  You can create a keypair at https://walletgenerator.net/ as well.  You can also do it via the wallet console.

-Fuse

I'll admit that the pictures don't really show their true characteristics.  They are heavy, thick, metallic coins.  Definitely something that will hold up over time.  I'm glad everyone likes them.  If for any reason there are any issues with any coins or orders, feel free to PM me or post in the following thread: https://bitcointalk.org/index.php?topic=890637.0.

-Fuse

Use of the hologram stickers:

I have included 2 stickers in with each coin.  This is in case you totally mess up putting it on or the first sticker gets tweaked somehow.  Either way, it's pretty straightforward.  There is a clear square in the middle of the hologram that will line up with the indent on the back of the coin.  You need to create a paper wallet key pair, and print it out on a paper no wider than 0.5" in one dimension.  It can be longer in the other dimension because it can be folded over.  See this post for more info on the wallet:


Additionally, you could use a qrcode, as long as you have a printer capable of high resolution at smaller sizes.  I was able to scan a wallet address as a QR code at a 0.5" x 0.5" size.  I haven't tested Bram's QR code generator with the added NLG image, but I think that would be even cooler.  You can find it here: http://guldencoinqrcode.nl/.

You could also just print the wallet address, and then keep the private key separate.  That way if you lose the coin, you never lose the digital coins loaded on it.  You could also do a two-factor key pair... it's really all up to you how you want to "load" the coin.

Once you have the paper wallet, I found it was easier to attach the paper to the hologram first and then attach the hologram to the coin.  I placed the hologram sticky side up on a flat surface and then carefully placed the paper on the sticker, aligning the sticker with the clear square in the middle.  Once the paper was attached, I used a paperclip as an applicator of sorts to put the sticker on the coin.  I didn't want my fingerprints to transfer to the sticker, or the oils on my hands to get on the coin.  So I pressed the paperclip against the sticker while it was on the table, and then I was able to pick up the sticker without handling it directly.  It also made it easier to place the sticker on the coin because my big fat fingers weren't in the way.

For reference, this is what it would end up like:



It's hard to write a good description of how I did all this, but I hope that helps.  If needed, I can post a video of how I do it when I get home tonight.

-Fuse

Sorry for the delay in that post... got wrapped up with my buddy digithusiast in the main thread.  Oh, the joys of being hated for no legitimate reason lol.

I will double post to keep the info clean.

-Fuse

What does me signing my posts have to do with anything?

If you read properly... you would have seen that Terk mentioned he was in talks with the devs, and that others had msgd him too.

As far as my commitment to NLG... yes, I want to make money.  We all do.  My team makes no money off my pool, though.  It's my pool.  Hell, I just make enough to cover my server fees every month.  I run a pool for NLG because I was asked to by a member of the team because they wanted an honest, reliable pool op.  The main reason I'm in NLG though is because I honestly think it's the one coin that's doing it right.  I've been around long enough to see that.  So I'm sorry that I got behind it early on, and I hold a lot of coin.  Get over it.

I didn't threaten.  I made a statement that I would be out, as well as my team, if some idiotic decision was made that would change the landscape as a whole.  You don't obviously don't understand how blockchains work.  It's apparent in your previous statements about what mining is for.  So I'm sorry, but I wouldn't take your advice for anything.  You have no clue what you're talking about.

-FUSE

Do you understand how blockchains work?  It's to allow transactions to continue to happen... not to put coins into circulation.  Without miners, coins don't move.

You could distribute the coins all you want, but without miners they are worthless.

-Fuse

Have you followed this thread at all over the last few months?

PMs were sent.  He's silent in his own thread.  He's a douche at best.

My thought is he is raping the coin because he can.  He may or may not drop off the coin when the profit isn't there.  If he continues regardless, it would be a PR nightmare for him.  There is no way he can explain using users' mining power to further his own agenda.

-Fuse

OK... let's take this at a more conservative pace then.  If the simulator is a day of work, let's push forward with testing DIGI on the simulator then.  When can you have this done?  Can we have data by the weekend?

As far as the excel output goes, why not just fmt.Println each block to a text file?  We can parse the data from there.  It doesn't need to be pretty as long as we can read the data.

-Fuse

Let's step back a second.

I am going to go on record as saying that I don't completely agree with 24Kilo's post.  I've messaged him in Criptoe chat to tell him the same.  We often have differences of opinions, and I think that's what makes my team strong.  24Kilo is my devil's advocate on almost everything I do, and I love him for it.

While parts of 24Kilo's statement are probably true, the fact of the matter is that for them to become true, Terk would need to alter his profitability algorithm to ignore the exit point on NLG.  He would need to take a decisive action to ignore his miner's profit to fulfill his personal vendetta against the coin.  That would not end well for him publicly.  I honestly don't think it will happen.  24Kilo and I went on for a week arguing about this... the difference between a profit script led multipool and a miner with a lot of hashrate.  We just need to make sure Terk doesn't turn into the latter.

That being said, if profit continues to drive Terk's operations, we won't have reason to worry.  DIGI will do it's job, and we'll be fine.  However, if he does play god with the hashrate, there is nothing that can be done to stop that, short of programming them out in the code(bans, blocking, whatever).  Anyone with enough hashrate can control a chain.  It's a fundamental principal of mining.

-Fuse

Glad to hear that the coins are hitting their destinations.  I am just about to head out the door to work, so give me about an hour or so to get their and get settled, and then I'll post info in the coin thread on how to do the hologram stickers.

-Fuse

Oh man... you're full of lulz.  One day you'll open your eyes and see the nose on your face.

I don't care what Terk's intention is, was, will be... doesn't matter at this point.  He's a shady pool op in my books now.  One that won't even speak for himself in his own thread.  One that uses mouthpiece lackeys to stick up for him instead of answering questions about whether or not he's skimming off the top instead of paying miners, why he's raping a coin because he thinks he's hashrate god, and why he won't answer for himself... ever.

You stand up for him blindly like an obedient lapdog.  Why?  For a few mLTC a day?  That's really sad.  I honestly feel sorry for you and those like you.

-Fuse

We did not test the shorter block time.  All testing was done with our current values.  The numbers Kilo has stated are mathematical inferences that can be derived from the proposed changes.  See my reply to /GJ about these numbers for clarification.

The change in block time is not a priority, nor is it a necessity.  It was an additional suggestion that would be beneficial in the long run, and something we can discuss at a later date.  It's a suggestion I fully stand behind though.  The Criptoe team will most likely test this in the future as well, and we'll provide data if it's requested by the dev team.



This is a concern for sure, but there are at least 3 other active NLG pools, including the coiniumserv pool that was announced recently.  Understand this though... I don't have an interest in running away with the network.  Unlike CM, we don't need to worry if my pool breaks 50%... we just need to readjust and spread the hashes.

Recently, 24Kilo has expressed interest running pools.  Another member of our team, Vesperwillow, has run pools for testing and private mining.  I'll see if I can help either one of them get a pool up and running to give the community additional options.

-Fuse

Don't get me wrong... I'm freaking ecstatic lol.  We'll finally take back our chain from CM.  Me this morning:



-Fuse