Show Posts
|
Pages: [1] 2 »
|
That begs the question, where does the NLG come from? Nocks is the seller. They may call it different things now but that was the setup
At this moment there are 477M Gulden in existence of which 415M are circulating. Of those 477M 190M was created in 2014 and the other 248M are since then found by miners as blockreward, that's where the NLG do come from, miners. Oh, and witnesses nowadays. I could explain how some of those Gulden that Nocks sells come on Nocks but it would feel awkward to do so. Nocks is an exchange.
|
|
|
Nocks is not a store that hangs a pricetag on a product at a price they see fit. It's an exchange where the price is determined by supply and demand. See https://www.nocks.com/trade/NLG-EURNow as an extra service you can buy Gulden at Nocks using iDeal or Bancontact but that's a frontend where you actually do a marketbuy on the exchange.
|
|
|
If you own a Raspberry and have GuldenD running on it there are some settings that could influence how well it works. If you are totaly unfamiliar with navigating a linux systme from the commandline and your RPI is working fine you do not have to do anything, if it ain't broken don't fix it. For these changes you need access to the commandline, either via VNC, SSH or by connecting a keyboard and monitor (TV with HDMI will work fine) to it. Then edit the file Gulden.conf using the command: `nano /opt/gulden/datadir/Gulden.conf`
1) When Phase-3 went live there were problems with high CPU and memory usage. We found some workarounds by then that alleviated the problem but are not necessary anymore since version 2.0.0.9 (Or even counterproductive now): ---------- maxmempool=20 <-- remove dbcache=20 <-- remove maxsigcachesize=4 <-- remove rpcthreads=1 <-- remove par=2 <-- remove minimallogging=1 <-- remove, this is now the default on RPIs
2) 'tweaks' that _are_ usefull on RPIs. (If you made changes to these before please check the values given below) --------- maxreceivebuffer=1024 <---- default = 5000 which is a bit high imo (5MB). maxsendbuffer=256 <---- 512 is also fine. maxconnections=60 <---- Around 50 or 60 is fine. Do not go higher than 75 on an RPI unless you know what you are doing.
These settings also apply on more beefy nodes running on a VPS although there you can go way higher on maxconnections= but that depends on how powerfull your (virtual) CPUs actually are.
3) Add the adress of one or two (more than two is not necessary) known stable and up to date nodes. By doing this your node connects to this one first which means it will probably elect it as the 'preferred download'. ---------- addnode=83.161.66.135 addnode=185.167.206.35
All of these also apply for beefier nodes running on VPSes and whatnot with the exeption of 'maxconnections='. More powerfull machines can go with a much higher number there depending on the exact power of your (virtual) CPUs. 400 or more is cool if it's faster than an Intel Atom and has 2GB RAM (ymmv).
|
|
|
In general the article is fine. One flaw is that the article classifies Yobit as suited for something which would be a bit far stretched.
|
|
|
I had Mammon in Support-Chat through the website yesterday and we walked through the steps to solve his problem. He hasn't returned so for now I asume the problem is solved.
|
|
|
ok... is there a merchant list I can reference where I can spend Gulden if I ever visit the country?
guldenmap.com
|
|
|
Will Nocks be adding USD? Price is always lower then bittrex when I have looked and I would rather get the coins as cheap as possible.
They would love to have added that last year. Latest news about this is to not expect this to happen in 2018, same with GBP. Banks are a bitch when you are dealing with crypto.
|
|
|
I understood that the 650BTC we hear about were raised by handing out Gulden shares which would be a part of the 110M NLG premine that is already spent, am I wrong with this assumption?
You are correct.
|
|
|
I have earned 3 witness amounts with my +-25000 witness account but only locked for 6 months, I wish I had put it in for 3 years . . .
When Phase-4 becomes active you can extend the lockingperiod and/or the amount of funds in that existing witnessaccount. extendwitnessaccount "funding_account" "witness_account" "amount" "time" For now you can go to the console and type "help extendwitnessaccount" and have a look at the helptext.
|
|
|
... which leaves G 5,760 for the rest of the smaller accounts. So if Gulden get's to be popular with people and let's say 10,000 accounts get into a 3 year witness program with G 20,000 each. Every account gets a daily interest of G 0.576. That's G 210.24 a year.
So if witness gets successful, it will result in an average yearly interest of 0.011%!
That calculation is slightly off.
|
|
|
I have a question regarding witnessing, if I start 1 with 25 000 Gulden , can I add another amount less then 5000 to the same witness account or does it always have to be 5000 and more. Is the 5000 requirement only for new witness accounts?
The witnessaccount needs to start with at least 5000G and a minimum of 331 days OR 10kGand a period of 1 month but this you already know. Starting with phase-4 you can extend existing accounts, both the locking period and the amount of funds in it. Have a look in your desktopwallet: Menu > Debugscreen > Console and there type 'help extendwitnessaccount' and have a good look. Yes, you can extend an existing account from 25000 to 25200 if you want, the new amount needs to be greater than the existing amount, increase needs not be a minmum of 5k.
|
|
|
Malcolm MacLeod [1:22 PM] 2.0.0.9 is available now as a recommended upgrade https://github.com/Gulden/gulden-official/releases/tag/v2.0.0.9 it will be tagged as an official release and announced later as soon as the AppImage (for linux is fixed) - The AppImage people have temporarily broken something in their system so I'm working with them to fix it before final release but e.g. windows and osx users don't need to wait for that.
|
|
|
Installed latest Gulden wallet 2.0.0.7 today and got this warning when starting the wallet: "Wallet contains a HD index error. this is not immediately dangerous but should be rectified as soon as possible. Please contact a developer for assistance"
1) This is a precautionary scan that has been added to the wallet to detect any users whose wallet has a problem that was caused by an issue we picked up and fixed already in a past build. 2) There is no immediate danger to funds or anything like that, but to prevent confusion in future its best to deal with it sooner rather than later.Steps to take: ----- 1) Ensure you have recovery phrase; Close software and back up wallet.dat safely (keep a copy of this) 2) Remove wallet.dat 3) Restore from recovery phrase 4) Ensure all accounts and etc. are as expected - this will be the case in 99.99% of cases and if it is then nothing further to do - if not then seek further assistance. 5) If some balance is missing first rescan. If some balance or an account is still missing: set a larger keypool `-keypool=30` and then rescan.
|
|
|
Make a screenshot of your wallet in it's current state to check balance and accountnames. Then just make a backup of your current wallet.dat and store it offline, then rename your wallet.dat to something like wallet16.dat (So that no wallet.dat is present anymore). Then install the latest 2.0-wallet and restore your wallet using your recoveryphrase. After first syncing you may need to rescan transactions once more if you have multiple accounts.
This way you have a restored but clean wallet and all your receivingaddresses from the past are still tied to your wallet.
Wallet.dat can be found here: - windows data directory: 1) Press (winkey) `❖`+`R` 2) Type `%APPDATA%\Gulden` into the run dialog. 3) Press `↵` enter key. - Or browse to C:\users\<yourusername>\AppData\roaming\Gulden\
---> After restoring with the recoveryphrase the wallet is not encrypted with a password, remember to do this again.
|
|
|
{ "pow2_phase": 3, "number_of_witnesses_raw": 325, "number_of_witnesses_total": 325, "number_of_witnesses_eligible": 106, "total_witness_weight_raw": 54210276, "total_witness_weight_eligible_raw": 54210276, "total_witness_weight_eligible_adjusted": 10284176, }
|
|
|
"PoW˛ - phase 2": { "status": "locked_in", "since": 776160
|
|
|
|