Bitcoin Forum
December 09, 2021, 12:04:19 PM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 21 »
321  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — 25TH OF SEPTEMBER V1.3 (DGW3) MANDATORY UPDATE on: September 25, 2014, 05:56:15 PM
Some seeds are up.. https://explorer.guldencoin.com/#/ is on the new chain.

We're waiting for some miners to have mined DGW3 blocks.
Once we have confirmed these blocks are handled well by the wallets, we will release those
322  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — 25TH OF SEPTEMBER V1.3 (DGW3) MANDATORY UPDATE on: September 25, 2014, 05:21:41 PM
https://forum.guldencoin.com/index.php?topic=556.0
323  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — 25TH OF SEPTEMBER V1.3 (DGW3) MANDATORY UPDATE on: September 25, 2014, 04:17:38 PM
45 minutes to fork. if you don't want to resync the whole chain please shut down your wallet until 1.3 is installed.
https://forum.guldencoin.com/index.php?topic=556.0
324  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — 25TH OF SEPTEMBER V1.3 (DGW3) MANDATORY UPDATE on: September 25, 2014, 12:09:32 PM
Nice timers... No pressure, right? Wink

I've opened a topic in which I will post progress updates: https://forum.guldencoin.com/index.php?topic=556.0

Please shut down your wallet at 18:30 CEST to avoid having to resync the blockchain!
325  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 23, 2014, 10:58:52 AM
Hello everyone,

DGW3
A few days ago I posted that we were thinking about changing our difficulty re-adjustment algorithm from KGW to DGW3. The main reason for this upgrade is the swing in blocktimes caused by jumping miners. I promised to give an update today.

Meanwhile, there has been some discussion about other methods that could also be beneficial to Guldencoin. BTM’s long coin maturity is an interesting idea that might make it into the coin when more discussion has taken place. For now we believe the change from KGW to DGW3 is the first thing we need to do and we hope it will be enough to stabilize the network blocktime.

The word 'we' is used often in this post.  Just for clarification, when you say 'we' you mean the 5 people at 'https://guldencoin.com/who-we-are'?  Or were other people involved in this decision to hardfork?  Please don't take this as a negative remark.. just trying to understand what exactly the process is to decide on implementing a major change like this.

With "we" I mostly mean the team yes. But the decision is based on multiple factors: results from our own research, external persons/devs that we have asked for opinion, and rhe feedback from the community.
326  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — 25TH OF SEPTEMBER V1.3 (DGW3) MANDATORY UPDATE on: September 22, 2014, 09:00:46 PM

[ ... ]

Are there statistics about how many % of the users use this wallet 1.2 with this option? Or was it also in the previous version already.

The seeds page displays some stats about connections the seeds have.
Alert function is configured since 1.1.6
327  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — 25TH OF SEPTEMBER V1.3 (DGW3) MANDATORY UPDATE on: September 22, 2014, 08:58:01 PM


this function in the guldencoin wallet is cool!

Yeah, works great this message sending option in the wallet for the upgrade!  Cool Also windows 7 gave a message popup! Nice.

Are there statistics about how many % of the users use this wallet 1.2 with this option? Or was it also in the previous version already.

Meanwhile at Guldencoin HQ:



 Wink
328  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — 25TH OF SEPTEMBER V1.3 (DGW3) MANDATORY UPDATE on: September 22, 2014, 07:07:19 AM
Just posting to say that the CripToe team will be ready for the update.  We'll be anxiously awaiting the source Smiley

-Fuse

Hardcoreminers will be ready for the update too.

Great to hear guys!
329  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 21, 2014, 08:53:58 PM
Hello everyone,

DGW3
A few days ago I posted that we were thinking about changing our difficulty re-adjustment algorithm from KGW to DGW3. The main reason for this upgrade is the swing in blocktimes caused by jumping miners. I promised to give an update today.

Meanwhile, there has been some discussion about other methods that could also be beneficial to Guldencoin. BTM’s long coin maturity is an interesting idea that might make it into the coin when more discussion has taken place. For now we believe the change from KGW to DGW3 is the first thing we need to do and we hope it will be enough to stabilize the network blocktime.

Another thing has popped up that needs to be taken care of.

Protocol version revert
When KGW was added to Guldencoin, the protocol version was used to reject old software from the network. This means that the protocol version is not in sync anymore with Litecoin and Bitcoin protocols. We would like to have it in sync again as this will make development easier and documentation for the given versions in the other coins will still apply to Guldencoin that way.

Version 1.3
Main changes are DGW3 and the protocol version revert and because of these changes, we need to perform a hard fork in the network. The new software version number will be 1.3 and it won’t be able to connect with pre-1.3 software. Updating your wallet is mandatory!

The plan
Times are CEST timezone (UTC+0200)
Thursday 25th of September we will cause a hard fork.
18:30 we will start by shutting down the seeds one by one.
19:00 the last seed will be shut down, the last block known by this seed will be the last KGW block.
19:01 We will hard code the next block number into the new software and start compilation of the guldencoind (software ran on the seeds).
19:05 We will start compiling the guldencoin-qt wallet for Windows and Mac OSx.
19:15 First seed is started with the new 1.3 software, other seeds follow one by one.
19:16 We test the guldencoin-qt wallet with the new network
19:17 New software source code is pushed to Github.
19:20 The new guldencoin-qt wallet is published on the website and available for download.

We will keep everyone updated about the process through a topic in the forums.

Exchanges, payment providers, etc.
We advise operators for automated systems to suspend processing the chain 2014-09-25 18:00:00 until the new wallet (v1.3) has been installed. We will approach as many operators as we can to inform them of these plans.

/GeertJohan
The Guldencoin Team

Topic about this on the Guldencoin forum: https://forum.guldencoin.com/index.php?topic=548.msg4668
330  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 20, 2014, 09:08:21 PM
I had a conversation with Kilo after he posted the BTM post.  In our discussion, he explained why BTM is a killer solution to the problems coins face with swings in hashrate and difficulty.  I'll give it this much, it's a brilliant approach to solving the problem.  However, it's an algorithm that is good from launch onward, not something you set midstream.  DGW3, Digishield, etc. don't alter the base mechanics/dynamics of the coin.  They only alter the process of accepting blocks into the chain.  Additionally, they don't require a hardfork.  The BTM solution needs a hardfork, and it changes major aspects of the coin.  As stated above, you're looking at around a 24 hour confirmation time with it.  That's a lot of time in which something could happen to the blockchain.  Maybe I'm daft, but I just don't see the benefit of the BTM solution over something like DGW3 or Digishield.

It's all going to even out mining in the end.  I say do whatever has the least amount of impact on the coin as a whole.  IMO, DGW3 or Digishield does that.

-Fuse

I am also happy to see the devs are looking at DGW3, most scrypt coins just do digishield because it is the easier option. I don't see any normal scrypt coins with dgw3? So it might make NLG unique in some weird way. Smiley

Easy/effective.  Pretty much why most coins go with it.

-Fuse

We won't be the first Scrypt coin with DGW3, there are at least 3 others.
The fun thing about the diff re-adjustment algo (digi, DGW3) is that it does not have to know the hashing algorithm (scrypt, X11). It simply modifies the difficulty by a factor, the factor is calculated based on the target time for the past n blocks (nTargetTimespan), and the actual time for the past n blocks (nActualTimespan). The factor is applied to the average difficulty for the past n blocks (PastDifficultyAverage and bnNew).

I've made a gist to make it easy for you guys to read the code: https://gist.github.com/GeertJohan/b28da8105babf0553f21

So basically the parameters that can be changed are the max/min factor applied (lines 56 to 61 in the gist) and the number of blocks that are taken into the calculation (lines 12,13 in the gist).
I'm looking into that and have asked Evan (DGW author) for comments.
331  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 20, 2014, 04:14:08 PM
@/GeertJohan, did you also consider the BTM solution to this problem? Why was it rejected? To me this seemed a very elegant solution to the problem (which should IMHO also be future-proof).

Ref: https://bitcointalk.org/index.php?topic=554412.msg8870691#msg8870691

Yes we are still thinking about the BTM solution of making the required confirmations for generated coins higher.
However, I think it can be bypassed by any jump pool fairly easy. The pool simply creates a buffer of say 100K NLG and places this at the exchange. When the pool decides to mine blocks, the buffer is being sold. So if the pool gets 14 blocks, then 14K NLG is sold at the exchange. When the 14K mined coins are completely confirmed (which will take longer than normal), the coins are moved to the buffer at the exchange, so the buffer is back at 100K NLG again.
I think this technique might actually be used already, it makes the calculations by a jump pool very accurate because mined coins can immediately be sold. The buffer itself is a one time investment that can eventually be sold again.

So when the generated coins maturity confirmations is changed from 120 to 240, that would simply mean that the jump pool requires a buffer of twice the size to accommodate for the confirmation time..
So like BTM, it would require a huge confirmation time (maturity), like 480 (20 hours), 720 (30 hours), 960 (40 hours) or maybe even 1152(48 hours)... Each one requiring a larger buffer to effectively calculate the profitability for mining and selling coins right away.. And even with a small buffer it would work, it would just mean that the miner can't come back every hour and has to wait for the buffer to fill for a day or two..
The downside is that our dedicated miners also have to wait longer before their coins are matured. So I would very much like to hear how everyone thinks about this. Especially if you are a miner (dedicated or jump), please let us know how you feel about a higher maturity confirmation count.

To add my 2 cents, I think that if a solution is implemented which needs a hardfork it has to be a futureproof solution of some sort and not another algo for an old problem.
The BTM solution is very nice and even if it takes an huge confirmation time to solve the problem it's also in the benefit of the miners. Right now the common miners and pools are put behind and only get the hard blocks. Thats a very undesirable situation not to talk about the fact one pool can dictate the coin by mining 90% of the total. Another solution to the problem can be rejecting blocks with relatively low blocktimes. This way it's no use to add a lot of hashrate because those blocks will be rejected. Drawback is the normal miners also get a rejected fast block once in a while, but in the long run they benefit because the big pools have less advantage. An variant could be an algo that prevents two fast blocks in a row.


I have also thought about that yes: rejecting blocks that are mined too soon. However, a miner could then mine the block in advance and broadcast it when the time is right.
So lets say the algorithm denies blocks with a timestamp within 20 seconds of the previous block. A jump pool operator could easily write some software to work arround this. The pool would generate 20 blocks in advance, each with a timestamp that is 20 seconds in the future relative to the previous block. Then the pool op would simply broadcast each block at exactly the right times. The pool's chain would automatically win as the normal miners simply can't generate blocks that fast. (edit: and they aren't coordinated to mine blocks in advance)
Please correct me if I'm wrong or if I'm overlooking something.
332  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 20, 2014, 03:38:16 PM
@/GeertJohan, did you also consider the BTM solution to this problem? Why was it rejected? To me this seemed a very elegant solution to the problem (which should IMHO also be future-proof).

Ref: https://bitcointalk.org/index.php?topic=554412.msg8870691#msg8870691

Yes we are still thinking about the BTM solution of making the required confirmations for generated coins higher.
However, I think it can be bypassed by any jump pool fairly easy. The pool simply creates a buffer of say 100K NLG and places this at the exchange. When the pool decides to mine blocks, the buffer is being sold. So if the pool gets 14 blocks, then 14K NLG is sold at the exchange. When the 14K mined coins are completely confirmed (which will take longer than normal), the coins are moved to the buffer at the exchange, so the buffer is back at 100K NLG again.
I think this technique might actually be used already, it makes the calculations by a jump pool very accurate because mined coins can immediately be sold. The buffer itself is a one time investment that can eventually be sold again.

So when the generated coins maturity confirmations is changed from 120 to 240, that would simply mean that the jump pool requires a buffer of twice the size to accommodate for the confirmation time..
So like BTM, it would require a huge confirmation time (maturity), like 480 (20 hours), 720 (30 hours), 960 (40 hours) or maybe even 1152(48 hours)... Each one requiring a larger buffer to effectively calculate the profitability for mining and selling coins right away.. And even with a small buffer it would work, it would just mean that the miner can't come back every hour and has to wait for the buffer to fill for a day or two..
The downside is that our dedicated miners also have to wait longer before their coins are matured. So I would very much like to hear how everyone thinks about this. Especially if you are a miner (dedicated or jump), please let us know how you feel about a higher maturity confirmation count.
333  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 20, 2014, 02:59:23 PM
Hello all,

I haven't posted a message on here over the past few weeks because I've been very busy with the difficulty problem.
Once it was discovered that the jump pool might be CleverMining I got in contact with Terk to discuss the problem.
He reduced the amount of hashrate for NLG a few times so it won't cause multiple hour blocktimes anymore.
Fuse also contacted Terk, and as you all know by now the hashrate used by CleverMining for NLG is now 1/12th of the normal hashrate they would use.

I want to thank Terk and CleverMining again for their cooperation and help.

However, CleverMining and other jump mining pools won't hold back forever, especially not when the prices rise.
So we need a solution.

I dug into the code.. I read the digishield and DGW1,2,3 algorithms and looked at some others.
Digishield looks a lot like the original diff adjustment algorithm. But it readjusts per block and rises diff slower, while it lowers diff faster.
This makes it possible for a jump pool to mine a lot of blocks, and afterwards the diff drops faster again.
DGW1 and 2 look a lot like DGW3. DGW3 simply has some improvements over the first two.
DGW also adjusts the difficulty per block. But it rises the diff just as fast as it lowers it.
But it calculates the new diff based on the average diffs for the past x blocks. This means the diff can rise fast when a lot of blocks are mined in a short amount of time, but it also levels back pretty quick afterwards.
I believe that DGW3 is our best option. We are now making plans for a mandatory update including this new algorithm. We will have more information available before the end of tomorrow (sun 21th).

Thanks,
Geert-Johan
334  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 13, 2014, 10:51:20 PM

... knip ...

It's already used in some coins.
I think coders can explain it better than me how it works.
It reads like the mod jumps in if something smells like a 51% attack and checks a number of blocks back in the chain for a possible fork.

Maybe WaterLooDown can explain/correct me?

I don't believe the problem here is 51% attacks. Chain rewrites do occur in the NLG network. This is expected with the low blocktime and varying hashrate, and is handled fine (just as in bitcoin and pretty much any other coin). I've inspected all chain rewrites since the the beginning of august and in 90% of the rewrites by G7f, G7f rewrites a block that only contains a generation transaction to G7f itself. So that doesn't really sound like a coordinated attack on other miners.

Do you maybe have some links to slingshot code? I can't really find it in Google.
edit: nevermind i've found it.
335  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 13, 2014, 07:40:26 PM
... knip ...

People that know me know I'm the last person to make stupid panicked decisions.  That being said, I think a form of Digishield, or similar, needs to be added to the roadmap ASAP.  That, or you just ask the pool to stop mining NLG.  Pool OPs are usually pretty respectful of coin devs.  The other option is to flat out block the IP range of the pool in the wallet code, and effectively just shut them out.  12 second block times aren't normal, regardless.  Especially with a difficulty of 300+.

-Fuse

If you have 100 GH/s, then 12 seconds at 300+ diff is a joke.
As said, we're looking into solutions (edit: yes, maybe digishield). Blocking an IP range is not on our list, it's not a solution.
336  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS Pre-Release on: September 13, 2014, 06:53:39 PM

...knip...

Anyone else noticing the extremely long lag on the blockchain right now?  It was like 2 hours of no updates, then all of a sudden we jumped 6 blocks.  My wallet, the seeds page, and the exchanges all had the same issue.

-Fuse

EDIT- Looks like the total network hashrate halved, and the block times are coming in faster than normal.  Not saying this is what it is, but I've seen this with coins being attacked with exploit attacks.  I would suggest pool ops keep an eye on your pools.

EDIT- Looks like we're cracking blocks every 5 seconds.  This isn't normal.

EDIT- https://explorer.guldencoin.com/#/address/Gf7wGAwJGDLfoHcNCRLKZqpk2EQU5ixA6c - our mystery wallet claiming all these blocks right now.


We're watching this closely right now..
What seems to have happened is that a jumppool/multipool mined until KGW changed the difficulty to 535 (block 116955).
After that the multipool left and the remaining miners had a hard time mining blocks.
A few hours later two blocks were mined and the difficulty dropped to 354 (block 116957). At that point the multipool started mining NLG again. Since about 2:30 hours of blocks were missing the KGW kept difficulty low so the pool could mine a lot of blocks very fast. Other miners also got some blocks, but G7f got most of them because they have a lot of hashing power.
We're now at block 117047 with diff 483. The last two blocks were not mined by the multipool, it seems they have left again.

The main problem here is the huge spike in block-time which causes delay in transactions being confirmed.
This is unacceptable and we're doing extensive research on the problem and are looking at some solutions. But don't expect huge changes too soon, it's important to make rational decisions and not jump too quickly in a situation like this. edit: As Jero said, the problem solves itself when more miners join the network (which happens when price rises). At that point the hashrate spikes of mining pools will become less noticable.
337  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS coming soon on: September 07, 2014, 04:08:44 PM
....

I wanted to find out the communities thoughts before I pursued this with you. I'm selective about it, that's all Smiley
I also haven't been able to to put my mind to crypto for the last week or 2, personal reasons.

No problem. Smiley Can you tell us a bit more about your proposal? What would it do? how would it work?
338  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS coming soon on: September 07, 2014, 04:02:30 PM
Hello Guldencoin Community!

I have been in contact with the OP owner about an idea I had for sustaining the amount of NLG in existence. While I did not get an excited reply from him, I didn't release my idea yet, but it's golden
(gulden) haha.

.. snip ...

Before I release my idea to the dev as I was instructed to do by the OP owner, .. snip ..

You were asked (not instructed) to email me with your idea, so we could discuss/brainstorm about it. Sadly, I have not received anything yet...

We are interested in your idea (why wouldn't we be). However, all information you have given so far is very abstract.  This problem of lost coins has been topic of discussion for a milion times in Bitcoin (and altcoin) communities. In the end, the problem in fixing it is in the implementation.
I would be very interested to know how you think something like this can be achieved.
339  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS coming soon on: September 07, 2014, 03:18:23 PM
Crosspost from this Guldencoin forum topic

Guldencoin Explorer beta
The Guldencoin team is continuously working to improve the fundamental tools that power the coin and serve this great community.
It's only a day ago that we migrated the forums to a more ddos-proof location, and now it's time to release our next project: the Guldencoin Explorer beta.

This is a block explorer that I've been working on for the past few weeks. It's a new explorer, written from scratch.
At this time the explorer supports basic functionality, more features will be added as development progresses.
Because this is new software, there is some precaution advised. Don't use this explorer as a definite source of information yet, as data could be missing.
For instance, support for non-standard transaction scripts is not available yet.

As this is a beta, the explorer might not have 24/7 uptime. It might crash and needs to restart for updates now and then.

If you notice a bug or mistake, please report this! We cannot fix what we don't notice.

Have fun!
https://explorer.guldencoin.com
340  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [NLG] Guldencoin.com/pay-here — Guldenwallet for iOS coming soon on: September 06, 2014, 03:36:00 PM
We're doing some migrations with the Guldencoinforum.com due to recent DDOS attacks.

Migrations are done. We're now at https://forum.guldencoin.com.
Old url's are being forwarded.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 21 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!