Meanwhile @ LTEX HQ:  Nice haha  |
|
|
|
A little bit of venting:I wanted to comment on the situation at the moment with DIGI, and some of the conversation being had over in the Gulden forums. While the discussion is in Dutch, hopefully Google translate isn't giving me the wrong translation. So there are some points I wanted to address. Op die manier hebben we Digi geimplementeerd, aan de hand van suggesties, ideeen en gevoelens, maar niet aan de hand van bewijzen. (Translated to:In this way we have implemented Digi, according to suggestions, ideas and feelings, but not on the basis of evidence. And it does not work, in fact the risk was even present it would work worse.) It has proven effective for a large number of altcoins. My team's suggestion for DIGI wasn't based on feelings, it's was based on the fact that DIGI works for a lot of other coins. It's just not working with our block times and the absence of dedicated miners. But I'll come back to the block times in a minute. Anyone else notice that as dedicated mining power reduced over the last week, things got progressively worse? People jumped ship and furthered the situation we're in now. Fact of the matter is we are playing ping-pong with CM. We find a long high block and CM finds the short block. There is no middle ground without dedicated miners. Top that off with my thoughts that we're moving too far in either direction means that we're never landing in a difficulty zone that accommodates our dedicated miners, and we're just struggling more than we need to right now. Back to block times. DIGI, and other single block retargets, work best with a block time closer to 1 minute. Lets do some math: Our block retarget = 150 seconds. Let's say the last block came in at 15 seconds. That's 10% of the retarget time. Let's say block retarget = 75 seconds. We have the same last block time of 15 seconds. That's 20% of the retarget time. Regardless of the change limit, you could guess which is getting a bigger proportional change to difficulty. So with our block times, not only are we hitting extreme retarget/actual block time proportions, but we're using a higher percentage of change. I'll admit that DIGI is a little wonky right now. However, it is the right algo for the situation. With dedicated mining power, DIGI will work in it's current form. CM will take less coins, and miners will make more profit. De tijd die GJ in de Digi implementatie heeft gestoken, heeft hij niet in de simulator of custom algoritme kunnen steken. Het lijkt dat het verwarrend blijft voor velen. (Translated to: The time GJ has put into the Digi deployment, he was unable to stabbing in the simulator or custom algorithm.) The translation is a little confusing, but there's one part that really stands out, even with the broken translation- the DIGI work took away from /GJ's ability to work on a custom algorithm. First thing to note about this is that we still haven't seen any results from the simulator. The last github commit was over a month ago. I still don't see the DIGI code in the simulator. While I would love /GJ's simulator to be the end all be all source of a new or custom algo, we haven't seen anything from it other than false hope. I know that sounds harsh, but it's how I feel. The simulator is still unproven. It will be so until it's tested against a testnet, and the results are reviewed by someone other than it's creator. Now if any of the translations were just totally off, and I'm reading it the wrong way, please let me know. Speaking of simulators:That being said, I wanted to share the latest developments out of the Criptoe team. We are still committed to providing any and all support we can for the coin. And while we agree that the simulator is a great idea, we're just GO dumb. So instead of learning GO, we wrote our own simulator. Let me rephrase that... our most recent addition to the team wrote our own simulator. So I would like to share his project with everyone now. I'll let him comment on the details when he gets online and sees this. The simulator is an Excel spreadsheet running a VBS macro scrypt on the backend. It's relatively easy to tweak the numbers to test out different situations, and there are already plans in the works to try to port it to C++ for easy algo code drop in. We know that there are different paths that one can take to get to a solution, so we forged our own instead of waiting for someone else. So without further ado, I present the Criptoe Mining Simulator: Settings page:  Mining results page:  European/NL Criptoe Mining Pool:In addition to our simulator, within the next couple weeks, the above mentioned member will be opening a European extension to the Criptoe pool. It will run separately from Criptoe.Com, under his control, and provide a backup pool to those looking for the reliability and trustworthiness that the Criptoe team strives for. We'll keep people up to date with launch info, so stay tuned. I'll leave with this- You may love the Criptoe Team or hate us. You may think we're a bunch of old opinionated bastards, 24Kilo especially(love ya, mate), but we're here to help in any way we can. We've been around long enough to see enough failures in crypto to know when you have a winner. NLG is our winner. Here's to the success of NLG, from now until the zombie robot apocalypse. -Fuse Excellent work Mr Fuse, will be interested to see your teams results. I personally appreciate the support you keep giving Guldencoin and I am team Criptoe fan! Same here  |
|
|
|
 There we go! Lift offfff! Congratulations! Nice one |
|
|
|
What would be the price that would make NLG non-attractive to CM?
Around 400-450 should be fine to make it less attractive and have less fluctuations in block times PROVIDED dedicated hashrate remain the same. 4-5 months ago it would of been possible to keep the price that low but now with so many buyers people will buy up coins at those bargain prices if anyone had to try force the market down. Guldencoin is at a place where a dump would reverse just as much as a pump. This is good! At which diff CM joins and with how much GHash? |
|
|
|
I'm still very happy with DIGI. Current situation is better than the past few months.
Good to hear. Hopefully it puts a lot less pressure on your wallet, mate. Lord knows you've been buying a ton of support for the chain for a long time now. I'm just really happy that pools that haven't seen 1% of the blocks in the last 5 months are now seeing almost 10%. That's a good feeling for me, even as the biggest pool now. -Fuse I'm really happy! We knew DIGI wasn't the perfect solution but it does what is needed kicking multipools from the chain and giving it back to the dedicated miners. |
|
|
|
Super news! I am so proud to be part of this community! Things get done. Big thanks to the people who invested in the IPO making it all happen and big hooray tho the Apple dev. |
|
|
|
Hello everyone! Since today www.cryptocorner.nl is working together with www.guldencoinfaucet.nl For a starter Cryptocorner made 500NLG possible for the faucet! Thanks Rogier for making this possible! If you guys want to keep this faucet up, you can make small donations at the adress below. GanQEwZTg2pGRhfZYPsBugysARKzAx2yZf Thank you guys! Made a small donation  |
|
|
|
Created a new wallet from source on 32-bit Linux without any problems.
Well done guys !
GJ: why is no new android wallet required ?
I'm going to guess because the android wallets are usually what they call a "lite wallet". It just represents your wallet on the blockchain without having to download the blockchain. Think about what would happen if you had to download the entire BTC blockchain to your phone via 3G to use an android wallet. OMG... I would want to kill myself. lol Long story short, it doesn't need to confirm blocks or mine or anything like that, so it wouldn't need the code that tells it to do that. -Fuse Just to add I have asked the android dev to add a new checkpoint after the digi change has taken place. From today and over the course of the next week we will be getting exchanges and services to update to the new wallets. Maybe you can also ask if he can add support to scan private keys like the litecoin android wallet? That would be a nice feature |
|
|
|
It says I was forced to stop. So it is not offline, think it just stopped for some reason? Maybe Frais can explain how and what? <edit>Same counts for http://howtobuyguldencoins.com/</edit> Strange?!?!?!  <edit>User 'Frais' has blocked your personal message.</edit> No PM's possible. So something is very wrong here I suppose... Anybody got some info |
|
|
|
Cool stuff |
|
|
|
|
I also back Fuse in this one fully simply because algorithm change is needed rather now then tomorrow! As there is no time frame given for the simulator and algo change. Don't get me wrong this is not a problem but we need a solution in the meantime.
As Clevermining is breaching the security of this coin and keeping price down.
By doing this it keeps new investors away old one leaving, making it not profitable for new miners to join
and so staying in this vicious circle
|
|
|
|
Considering the conversation has been taken to the Dutch section of the Gulden forum, I'm going to take it that my input isn't welcome anymore. Either way, if Google translate is halfway correct and I'm reading it right, Rijk and the team will look at ready to pull Git code. So I updated the git-pull, correcting the errors that /GJ noted. https://github.com/nlgcoin/guldencoin/pull/8Stop making excuses, stop dragging your feet, and just fix the damn algorithm already. -Fuse Your input is still very welcome Fuse really! No negative words regarding you or your team. |
|
|
|
Nederlands
1. Uitdaging
Inmiddels is iedereen van onze uitdaging op de hoogte, dit is al lange tijd aan de gang en nu is het clevermining, maar iedere andere multipool kan dit natuurlijk ook doen.
2. DGW3
Nadat we erachter kwamen dat DGW3 niet hielp, is Geert-Johan aan de slag gegaan met de simulator. Een simulator waarmee hij bestaande, maar ook zelf-ontwikkelde algo’s kan testen. Deze simulator ontwikkeld hij volledig zelf, het is geen kant-en-klaar pakket. Dit is dus veel werk en kost veel tijd.
3. Simulator
De eerste versie van de simulator is klaar en staat op Github, hier kunnen ontwikkelaars dus al mee aan de slag. Uiteraard is Geert-Johan ook verder gegaan met ontwikkelen van de simulator.
4. Wanneer?
Er zijn een heleboel vragen over wanneer deze ontwikkeling klaar is, helaas is daar geen antwoord op. Dat klinkt misschien bot, maar het is het enige eerlijke antwoord. We weten het niet. Het is klaar wanneer het klaar is. Gaat het een oplossing opleveren? Ja.
5. Opensource
De Guldencoin source is voor iedereen beschikbaar, iedereen kan ermee aan de slag en op zoek naar een oplossing. Wij hebben een bepaald pad gekozen (simulator en dan eigen algo), maar een andere ontwikkelaar kan natuurlijk voor een ander pad kiezen. Uiteindelijk bepalen we met z’n alleen wat er geïmplementeerd moet worden, decentraal. Wij zijn niet de baas of verantwoordelijke instantie.
6. Verantwoordelijk
Jij bent verantwoordelijk en de rest van de community. Als jullie zeggen dat wij iets moeten implementeren, dan doen wij dat. Zo gaat dat ook met DIGI, maar Geert-Johan kijkt gelukkig naar de code voordat hij iets implementeert. En in dit geval zag hij dat er dingen niet klopte, dingen die hadden gezorgd voor grote problemen. Veel groter dan de uitdaging die we nu hebben. Maar nu kan Geert-Johan natuurlijk niet zomaar zeggen, het klopt niet. Hij moet het onderbouwen en bespreken met degene die de code heeft aangeleverd, Fuse in dit geval. Na dit gesprek is er besloten deze code niet te implementeren, maar verder uit te werken.
7. Decentraal
Stel Geert-Johan had niet naar de code gekeken, of hij had niet ontdekt dat de code niet goed was, dan hadden we dit geïmplementeerd. Omdat de community erom vroeg, het is decentraal dus de meerderheid beslist. Heel simpel. Besef dus goed dat er grote verantwoordelijkheid bij komt kijken. Iedereen heeft die verantwoordelijkheid, jij beslist mee over de toekomst van Guldencoin.
8. Wat nu?
Geert-Johan gaat verder met de simulator en neemt nu ook DIGI mee bij het testen, als daar uitkomt dat DIGI de oplossing is, dan wordt dat natuurlijk geïmplementeerd. Als DIGI niet de oplossing is, gaat Geert-Johan verder met het ontwikkelen van ons eigen algo. Dit is het pad wat wij volgen en volgens ons is dit de enige oplossing. Let op, dit is volgens ons. Andere ontwikkelaars kunnen natuurlijk ook aan de slag, uiteindelijk beslist de community.
9. Communicatie
Ook daar zijn veel vragen over, met als meestgestelde: Wanneer is het klaar? Dat kan ik me goed voorstellen, maar helaas is het antwoord kort: wanneer het klaar is. Zo is het nou eenmaal. Ik heb Geert-Johan gevraagd om alleen te focussen op de ontwikkeling en niet op updates. Hij kan niet aangeven wanneer het klaar is, maar wel dat hij het gaat oplossen. Mogelijk kunnen andere ontwikkelaars dit wel aangeven en een duidelijke roadmap verstrekken.
10. Samenvatting
Wij zijn een klein onderdeel van Guldencoin, ontwikkelen op onze manier voor Guldencoin. Wij gaan het multipool probleem oplossen, maar kunnen niet aangeven hoe lang dit duurt. Guldencoin is decentraal, wij luisteren naar de meerderheid. Iedereen kan werken aan de oplossing.
English
1. Challenge
By now everyone is up to date on the challenge we face, this has been going on for a while and at the moment we’re facing Clevermining, but any other multipool can do this.
2. DGW3
When we found out that DGW3 didn’t help, Geert-Johan started to work on the simulator. A simulator used to test existing, but also self-developed, algorithms. He is developing this simulator from the ground up, it is not some simulator that is already ready. This takes a lot of work and time.
3. Simulator
The first version of the simulator is ready and is available on Github, other developers can use this simulator now too. Geert-Johan continued work on the simulator of course.
4. When?
There are a lot of questions about when the development will be ready, unfortunately there is no answer for that question. That might sound rude, but it is the only honest answer. We don’t know. It’s done when it’s done. Is it going to provide a solution? Yes.
5. Opensource
Guldencoin source is available for everyone, anyone can get to work and find a solution. We have chosen a certain path (simulator and then our own algo), but another developer can choose a different path. Eventually we all dictate what is implemented into the code, decentral. We, the team, are not the boss or responsible institution.
6. Responsibility
You are responsible and the rest of the community. If you say that we have to implement something, we will. That is what’s happening with DIGI, but Geert-Johan looks at the code before he implements something. And in this case he saw that some things didn’t add up, things that could’ve caused bigger problems. Bigger than we’re facing now. But Geert-Johan can’t just say that something isn’t right. He needs to present proof and discuss this with the person that delivered the code, in this case Fuse. After this conversation it was decided not to implement this code, but further development was chosen.
7. Decentral
If Geert-Johan didn’t look at the code, or hadn’t discovered that the code wasn’t good, we would’ve implemented it. Because the community asked for it, it is decentral, so the majority decides. Very simple. Realize that this comes with huge responsibility. Everyone has that responsibility, you help decide Guldencoin’s future.
8. What now?
Geert-Johan is continuing work on the simulator and will test DIGI too, if the outcome says that DIGI is the solution, that will be implemented. If DIGI is not the solution, Geert-Johan will continue the development of the custom algorithm. This is the path that we are following and is, according to us, the only solution. Note, according to us. Other developers can look for a different solution, in the end the community decides.
9. Communication
There are a lot of questions about this, with most frequently: When is it done? I can understand that, but unfortunately the answer is short: when it’s done. That’s the way it is. I have asked Geert-Johan to just focus on development and not on updates. He can’t say when it’ll be done, but he will solve it. Maybe other developers can give this information and present a specific roadmap.
10. Summary
We are a tiny part of Guldencoin, developing our own way for Guldencoin. We are solving the multipool issue, but we can’t say how long it will take. Guldencoin is decentral, we listen to the majority.
Everyone can help find a solution.
Nice to hear from you again Rijk happy new year! |
|
|
|
Even the miners there are questioning what is happening with CM. Missing payouts, Terk being absent, etc. I don't understand how anyone could run a pool like that and continue to gain miners.
CM has a single point of failure (Terk went missing)? Oh, yes, please. Let CM drop from the planet. That would be a nice new year's gift! |
|
|
|
Clever is hitting us hard again  |
|
|
|
Below is a copy/paste from the OPAL-team. I think it's definetaly worth to consider if NLG still likes being listed at coin-swap. "This morning it came to our attention that Coin-Swap.net had been purchased by GAWMiners, which disturbed me a bit to say the very least. Coin-Swap’s past owner, Ian, was and is still a great friend of the Opal Team, and we congratulate him that he was able to profit from his exchange, as he deserves it. However, over the past few days it has come to our attention that Paycoin may not be everything it was claimed to be. There are multiple reasons people have called Paycoin a scam, and while it is unclear at this point, there are too many red flags for the Opal Team to trust GAW with our communities Opal, no matter how large or small. These red flags include: - A promise to the community to purchase Paycoin’s at $20/coin ( https://i.imgur.com/OVQdmym.png), which is four times the current price of Paycoin. GAW has tried to hide this promise ( https://archive.today/W3OTH), and has shown they cannot be trusted. - In an audit by Opal’s lead dev, Whit Jack, he discovered that special addresses stake at a rate up to 350%, which was never publicly disclosed, again proving they are not trustworthy. This has been verified by other users. These reasons, plus a few more have caused us to request Coin-Swap delist Opal, as both a protection for our community, and as a stand against GAW and other companies that prey on cryptocurrency users. ~The Opal Team". edit; further did I read on BCT that DOGE and LTC also asked for delisting. Thank for the heads up this is a very valid excuse to get delisted of coinswap. Don't think anyone uses it anyway. So I hope the dev team will contact coinswap to get delisted. |
|
|
|
Happy new year from holland! |
|
|
|
Lady's and gentlemen I've got them!  Tanks for the extras LTEX |
|
|
|
 NederlandsDe afgelopen weken hebben we de discussie omtrent de difficulty readjustment van dichtbij gevolgd en het is duidelijk geworden wat de volgende stap moet zijn. Nu is het tijd om die stap te zetten. De komende dagen zullen wij meer informatie hierover verstrekken. We zullen nauw samenwerken met ontwikkelaars in de community om ervoor te zorgen dat het een soepele overgang wordt. Als je zorgen of bezwaren hebt, maak ze bekend op het officiele forum: https://forum.guldencoin.com/index.php?topic=745.0EnglishFor the last weeks we’ve been following the difficulty readjustment discussion closely and it is clear what the next step should be. Now its time to take that next step. In the coming days we will provide more information about this. We will work closely with developers in the community to make sure it will be a smooth transition. If you have any concerns or objections please make them known at the official forum: https://forum.guldencoin.com/index.php?topic=745.0Bump, because of new page and the most important topic today ofcourse Really exited to see this! |
|
|
|
To cut this long reply short: My vote goes to Digi ASAP...
Same here! |
|
|
|
|
Show Posts
