Topic: Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 153. (Read 785531 times)
March 28, 2016, 12:32:46 PM
March 28, 2016, 01:38:24 AM
| NIRO | ▄▄▄ ▀███████▄▄▄ ▀██████████████▄▄▄▄ ▀██████▌╙▀▀▀▀▀█████████▄▄▄ ▀█████▄ ╙╙╙▀▀▀▀▀▀▀BA∞∞, ▀█████▄ ▀█████▄ ╙█████▄ ╙█████▄ ▄██████ ▐█████, ██ ╒██████████████▌ ╙█████▄ ▄██████╜ ██L ▐██ ▄██████████████▄ ███▀▀███▄ ██▌ ▐██▀▀▀▀▀▀▀▀▀▀▀▀ ╙▀████▄ ▄██████╜ ██▌ ███ ███▀▀╙╙╙╙"╙╙╙▀▀██▌ ███ ▀███▄ ██▌ ▐██ ╓╓ ▀██████████╜ ██▌ ███ ██▌ ███ ╙███▄ ██▌ ▐██ ████ ▀██████╜ ██▌ ███ ▀███████████████▄ ███ ╙███▄,,██▌ ▐██ ╙▀▀▀ ▄ ▀████, ██▌ ███ ▄▄╙"▀▀▀▀▀▀▀▀▀▀▀███ ███ ╙▀█████▌ ▐██, ▄███▄ ▀███▄ ███ ███ ██▄ ███ ███ ▀███Ü ▐██████████████▌ ▄██████ ▀███▄ ╙█████████████████` ▀████████████████ ╙ ╙╙╙╙╙╙╙╙╙╙╙╙` ▄██████╜ ╙███▄ '╙"▀▀▀▀▀▀▀"╙ ╙"▀▀▀▀▀▀▀ 4██████╜ ╙███▄ ▄▄▄ ▄µ ╔▄ ╓▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄ ╙███▄ ▐████▄ █▌ ██▒ ██ ██ ██▀╙╙╙╙╙╙▀█▌ ╙▀████▌ `██▄╠█▌ ██▒ ██ ╓▄▄█▀ ██ ██ ▀██▌ ╙███▌ ██▒ ██ ██ ██▄,,,,,,▄█▌ ▀█▄ ╙▀` ╙▀ ╙▀ ╙" ▀▀▀▀▀▀▀▀▀▀ ▀█▄ ╙█▄ ▀▄ | | PURE SHA3 | CPU/GPU | nPOS | 15 Active Innovations | MORE TO COME |
Code:
[table][tr][td][url=https://nexusoft.io][font=Arial Black][size=25pt][color=#111][b]N[color=#222]I[color=#333]R[color=#444]O[/td]
[td][font=monospace][size=1pt]
[color=#549FCE]▄▄▄[/color]
[color=#549FCE]▀███████▄▄▄[/color]
[color=#549FCE]▀███[/color]███[color=#549FCE]████████▄▄▄▄[/color]
[color=#549FCE]▀███[/color]███▌╙▀▀▀[color=#549FCE]▀▀█████████▄▄▄[/color]
[color=#549FCE] ▀███[/color]██▄ ╙╙╙▀[color=#549FCE]▀▀▀▀▀▀BA∞∞,[/color]
[color=#549FCE]▀██[/color]███▄
[color=#528FD2]▀██[/color]███▄
[color=#528FD2]╙██[/color]███▄
[color=#528FD2]╙██[/color]███▄ ▄██████
[color=#a3a3a3]▐█████, ██ ╒██████████████▌[/color] [color=#528FD2]╙█[/color]████▄ ▄██████╜ [color=#4479B3]██L [color=#C6DFEE]▐██ ▄███[/color]███████████▄[/color]
[color=#9e9e9e]███▀▀███▄ ██▌ ▐██▀▀▀▀▀▀▀▀▀▀▀▀ [/color] ╙▀████▄ ▄██████╜ [color=#5593D8]██▌ [color=#C6DFEE]███ ███[/color]▀▀╙╙╙╙"╙╙╙▀▀██▌[/color]
[color=#8f8f8f]███ ▀███▄ ██▌ ▐██[/color] ╓╓ ▀██████████╜ [color=#4B82C0]██▌ [color=#B0D8EC]███ ██[/color]▌[/color]
[color=#8a8a8a]███ ╙███▄ ██▌ ▐██[/color] [color=#53A8EA]████[/color] ▀██████╜ [color=#4B82C0]██▌ [color=#94CFE6]███ ▀█[/color]██████████████▄[/color]
[color=#828282]███ ╙███▄,,██▌ ▐██ [/color] [color=#53A8EA]╙▀▀▀[/color] ▄ ▀████, [color=#3B6493]██▌ ███ ▄▄╙"▀▀▀▀▀▀▀▀▀▀▀███[/color]
[color=#8f8f8f]███ ╙▀█████▌ ▐██,[/color] [color=#4F99E7]▄███▄[/color] ▀███▄ [color=#396597]███ ███ ██▄ ███[/color]
[color=#9e9e9e]███ ▀███Ü ▐██████████████▌ [/color] [color=#4F99E7]▄██████[/color] ▀███▄ [color=#295585]╙█████████████████` ▀████████████████[/color]
[color=#a3a3a3] ╙ ╙╙╙╙╙╙╙╙╙╙╙╙`[/color] [color=#4F99E7]▄██████╜[/color] ╙███▄ [color=#3F76B7]'╙"▀▀▀▀▀▀▀"╙ ╙"▀▀▀▀▀▀▀[/color]
[color=#4F99E7]4██████╜[/color] ╙███▄ ▄▄▄ ▄µ ╔▄ ╓▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄
╙███▄ ▐████▄ █▌ ██▒ ██ ██ ██▀╙╙╙╙╙╙▀█▌
╙▀████▌ `██▄╠█▌ ██▒ ██ ╓▄▄█▀ ██ ██
▀██▌ ╙███▌ ██▒ ██ ██ ██▄,,,,,,▄█▌
▀█▄ ╙▀` ╙▀ ╙▀ ╙" ▀▀▀▀▀▀▀▀▀▀
▀█▄
╙█▄
▀▄[/td]
[td][size=8pt][b][url=https://bitcointalksearch.org/topic/nexus-pure-sha3-cpugpu-npos-15-active-innovations-more-to-come-657601][color=#08298A][size=8pt]| PURE SHA3 | CPU/GPU | nPOS | 15 Active Innovations | MORE TO COME [/b][/size][/td][/tr][/table]
donate please: 2RV7XfZkmdnns57NiCDCuu6KVvhiNyviCnq1GEBpNXAmQjCC3w9
thank you
March 27, 2016, 05:13:01 PM
been focused the last years on DMD Diamond but from time to time scan the other crypto currencies
seems i missed NEXUS there few times but few days ago finally found it and found time read deeper
have to say that might be a hidden gem
we just researching if adapt some of the nice stuff Viz invented to DMD Diamond make sence
i added some NIRO to my crypto portfolio
seems i missed NEXUS there few times but few days ago finally found it and found time read deeper
have to say that might be a hidden gem
we just researching if adapt some of the nice stuff Viz invented to DMD Diamond make sence
i added some NIRO to my crypto portfolio
March 23, 2016, 04:01:53 PM
Google has a dwave its not a true general purpose quantum computer, it is also unsuitable to run shors algo which would be necessary to crack priv keys used in crypto.
March 23, 2016, 09:21:26 AM
I read somewhere here Viz saying that Merkle tree implementation in Nexus is in development, is this Merkle tree signatures what he was talking about?
SigmaX/Curecoin 2.0 will be using Merkle trees of Lamport signatures, Viz's implementation may (probably) differs it would be best to ask him to expand on his ideas but the basic principal is the same yes. I highly encourage anyone interested in cryptography to read the CC white paper it is very informative.
Some forums comments seem interesting
Hey! It is a lot of info, although it's a bit more concise here, the Bitcointalk forums have more of the design rational explained.
Currently, everyone has coins on only the 1.0 network--2.0 has not launched yet. At the launch of 2.0 coins, people will be able to convert 1.0 coins to 2.0, but they don't have to immediately. There'll be a fairly long grace period for people to convert their 1.0 holdings to 2.0.
Basically, it boils down to this: whether your coins are still on the 1.0 network or have been converted to the 2.0 network, they'll be eligible to receive SigmaX.
Timeline looks something like this: SigmaX beta (next week-ish), community testing. Curecoin 2.0 beta based on the SigmaX beta, community testing. Once we're happy with everything, Curecoin 2.0 full public launch. Then a few weeks later, SigmaX full launch.
Current plans are to do a time-released payout scheme on SigmaX. So basically, every week (for probably a year), either part of a premine or a block subsidy will mature on the SigmaX network. We'll aggregate all of the balances of users who wish to receive SigmaX (which everyone holding Curecoin should want, it's free SigmaX) on the cc1.0 and cc2.0 networks, and perform the appropriate payouts. This allows people to, during this year, fold to earn (or purchase on exchanges) Curecoin, and receive SigmaX.
People tie their cc1.0 or cc2.0 address to their SigmaX address by signing a message containing their SigmaX address with their cc1.0 or cc2.0 address. If someone on cc1.0 decides to move to cc2.0, they burn their coins, receive cc2.0, and sign the same (or a different) SigmaX address with their new cc2.0 address.
Why I am posting this here? in the case Nexus has to go through a similar process and a Nexus 2.0 had to be implemented to make it better, we could do the same thing, if big changes had to be made to the core, better be done early while very few people involved and little adoption than wait to have big infrastructure and tons of user like Bitcoin, where to make even a small change its like having a presidential election.
Quantum computers are a reality, not fiction not a dream anymore, Google has one already and they are finding ways to add more and more qubits to them to make them more powerful, and for some of the videos that I've seen on them they will be very good at braking encryption (fuckers), go to 5:40 minutes https://www.youtube.com/watch?v=JhHMJCUmq28
I will have a read to the white paper, still think Nexus will bring massive changes to crypto
March 23, 2016, 08:50:34 AM
I read somewhere here Viz saying that Merkle tree implementation in Nexus is in development, is this Merkle tree signatures what he was talking about?
SigmaX/Curecoin 2.0 will be using Merkle trees of Lamport signatures, Viz's implementation may (probably) differs it would be best to ask him to expand on his ideas but the basic principal is the same yes. I highly encourage anyone interested in cryptography to read the CC white paper it is very informative.
March 23, 2016, 07:53:48 AM
Neither says in specs what is the hashing algorithm they are using, In 2016 security of all these blockchains and cryptos are not a main concern in the future it will be.
On this subject of security i thought i would just let everyone know about Curecoin, they are currently running testnet for SigmaX a spin off of the new tech developed for Curecoin 2.0. They are currently testing new code for quantum-resistant signatures and mini-blockchain just to name a few features in the new code. If ur interested to know more u can browse https://bitcointalk.org/index.php?topic=603757.3220 just a few pages either side will have you up to date.
Yes, was reading this article few days back but couldn't find what are they using to encrypt this SigmaX coin (terrible name btw), though they are not the only ones besides Nexus focusing on this aspect, MaidSafe is using RSA 4096, http://blog.maidsafe.net/2015/01/29/consensus-without-a-blockchain/ go to Cryptographic Signatures in the second paragraph.
Problem with RSA is this http://danielpocock.com/rsa-key-sizes-2048-or-4096-bits.
I trust more Elliptical-Curve Cryptography than RSA
SigmaX and Curecoin 2.0 will both use merkle tree signatures, you can read from their white paper http://1.curecoinmirror.com/Curecoin%20Signatures%20Compressed.pdf or briefly about them on wiki https://en.wikipedia.org/wiki/Merkle_signature_scheme
I read somewhere here Viz saying that Merkle tree implementation in Nexus is in development, is this Merkle tree signatures what he was talking about?
March 23, 2016, 06:34:56 AM
Neither says in specs what is the hashing algorithm they are using, In 2016 security of all these blockchains and cryptos are not a main concern in the future it will be.
On this subject of security i thought i would just let everyone know about Curecoin, they are currently running testnet for SigmaX a spin off of the new tech developed for Curecoin 2.0. They are currently testing new code for quantum-resistant signatures and mini-blockchain just to name a few features in the new code. If ur interested to know more u can browse https://bitcointalk.org/index.php?topic=603757.3220 just a few pages either side will have you up to date.
Yes, was reading this article few days back but couldn't find what are they using to encrypt this SigmaX coin (terrible name btw), though they are not the only ones besides Nexus focusing on this aspect, MaidSafe is using RSA 4096, http://blog.maidsafe.net/2015/01/29/consensus-without-a-blockchain/ go to Cryptographic Signatures in the second paragraph.
Problem with RSA is this http://danielpocock.com/rsa-key-sizes-2048-or-4096-bits.
I trust more Elliptical-Curve Cryptography than RSA
SigmaX and Curecoin 2.0 will both use merkle tree signatures, you can read from their white paper http://1.curecoinmirror.com/Curecoin%20Signatures%20Compressed.pdf or briefly about them on wiki https://en.wikipedia.org/wiki/Merkle_signature_scheme
March 23, 2016, 06:00:51 AM
Just found this info, don't even know what exactly is about cuz is too much text, i'll just paste what matters to us.
Will GnuPG ever support RSA-3072 or RSA-4096 by default?
Probably not. The future is elliptical-curve cryptography, which will bring a level of safety comparable to RSA-16384. Every minute we spend arguing about whether we should change the defaults to RSA-3072 or more is one minute the shift to ECC is delayed. Frankly, we think ECC is a really good idea and we'd like to see it deployed as soon as humanly possible.
I think I need larger key sizes.
By all means, feel free to generate certificates with larger keys. GnuPG supports up to 4096-bit keys.
11.3 Do other high-security applications use RSA-2048?
2048-bit RSA is commonly used to secure SSL root signing certificates. It’s also used to sign operating system patches, Authenticode signatures, Java applets and more. RSA-2048 is believed to be safe against attack until at least the year 2030, so use it with confidence.
11.4 Why doesn’t GnuPG default to using RSA-4096?
Because it gives us almost nothing, while costing us quite a lot.
Breaking an RSA-10 key requires you to try each prime number between two and one hundred. There are twenty-five of these, meaning RSA-10 is equivalent to about a 5-bit symmetric cipher. Breaking an RSA-20 key requires you to try each prime number between two and one thousand: there are 168 of them, meaning RSA-20 is equivalent to about an 8-bit cipher. Doubling the keylength (from RSA-10 to RSA-20) didn't give us the benefit that we naively expected. Each additional bit gives correspondingly less in the way of additional security, and we quickly reach a point of diminishing returns.
That point of diminishing returns happens around RSA-2048. Once you move past RSA-2048, you’re really not gaining very much. At the same time, moving past RSA-2048 means you lose the ability to migrate your certificate to a smartcard, or to effectively use it on some mobile devices, or to interoperate with other OpenPGP applications that don’t handle large keys gracefully.
If you really want a 4096-bit RSA key there’s nothing stopping you: but we sincerely believe the overwhelming majority of users will be well-served with RSA-2048.
11.5 Why do people advise against using RSA-4096?
Almost always when people use 4096-bit RSA they’re doing so because they believe RSA-4096 to be much stronger than it is. The United States’ National Institute of Standards and Technology (NIST) states that RSA-2048 gives roughly 112 bits of security and RSA-3072 gives roughly 128. There is no formal recommendation on where RSA-4096 lies, but the general consensus is that it would come in somewhere around 140 bits — 28 bits of improvement over RSA-2048. This is an improvement so marginal that it’s really not worth mentioning.
If you need more security than RSA-2048 offers, the way to go would be to switch to elliptical curve cryptography — not to continue using RSA.
Nexus SK-1024 FUCKING RULES !
Will GnuPG ever support RSA-3072 or RSA-4096 by default?
Probably not. The future is elliptical-curve cryptography, which will bring a level of safety comparable to RSA-16384. Every minute we spend arguing about whether we should change the defaults to RSA-3072 or more is one minute the shift to ECC is delayed. Frankly, we think ECC is a really good idea and we'd like to see it deployed as soon as humanly possible.
I think I need larger key sizes.
By all means, feel free to generate certificates with larger keys. GnuPG supports up to 4096-bit keys.
11.3 Do other high-security applications use RSA-2048?
2048-bit RSA is commonly used to secure SSL root signing certificates. It’s also used to sign operating system patches, Authenticode signatures, Java applets and more. RSA-2048 is believed to be safe against attack until at least the year 2030, so use it with confidence.
11.4 Why doesn’t GnuPG default to using RSA-4096?
Because it gives us almost nothing, while costing us quite a lot.
Breaking an RSA-10 key requires you to try each prime number between two and one hundred. There are twenty-five of these, meaning RSA-10 is equivalent to about a 5-bit symmetric cipher. Breaking an RSA-20 key requires you to try each prime number between two and one thousand: there are 168 of them, meaning RSA-20 is equivalent to about an 8-bit cipher. Doubling the keylength (from RSA-10 to RSA-20) didn't give us the benefit that we naively expected. Each additional bit gives correspondingly less in the way of additional security, and we quickly reach a point of diminishing returns.
That point of diminishing returns happens around RSA-2048. Once you move past RSA-2048, you’re really not gaining very much. At the same time, moving past RSA-2048 means you lose the ability to migrate your certificate to a smartcard, or to effectively use it on some mobile devices, or to interoperate with other OpenPGP applications that don’t handle large keys gracefully.
If you really want a 4096-bit RSA key there’s nothing stopping you: but we sincerely believe the overwhelming majority of users will be well-served with RSA-2048.
11.5 Why do people advise against using RSA-4096?
Almost always when people use 4096-bit RSA they’re doing so because they believe RSA-4096 to be much stronger than it is. The United States’ National Institute of Standards and Technology (NIST) states that RSA-2048 gives roughly 112 bits of security and RSA-3072 gives roughly 128. There is no formal recommendation on where RSA-4096 lies, but the general consensus is that it would come in somewhere around 140 bits — 28 bits of improvement over RSA-2048. This is an improvement so marginal that it’s really not worth mentioning.
If you need more security than RSA-2048 offers, the way to go would be to switch to elliptical curve cryptography — not to continue using RSA.
Nexus SK-1024 FUCKING RULES !
March 23, 2016, 05:46:40 AM
Neither says in specs what is the hashing algorithm they are using, In 2016 security of all these blockchains and cryptos are not a main concern in the future it will be.
On this subject of security i thought i would just let everyone know about Curecoin, they are currently running testnet for SigmaX a spin off of the new tech developed for Curecoin 2.0. They are currently testing new code for quantum-resistant signatures and mini-blockchain just to name a few features in the new code. If ur interested to know more u can browse https://bitcointalk.org/index.php?topic=603757.3220 just a few pages either side will have you up to date.
Yes, was reading this article few days back but couldn't find what are they using to encrypt this SigmaX coin (terrible name btw), though they are not the only ones besides Nexus focusing on this aspect, MaidSafe is using RSA 4096, http://blog.maidsafe.net/2015/01/29/consensus-without-a-blockchain/ go to Cryptographic Signatures in the second paragraph.
Problem with RSA is this http://danielpocock.com/rsa-key-sizes-2048-or-4096-bits.
I trust more Elliptical-Curve Cryptography than RSA
March 22, 2016, 11:36:12 PM
Neither says in specs what is the hashing algorithm they are using, In 2016 security of all these blockchains and cryptos are not a main concern in the future it will be.
On this subject of security i thought i would just let everyone know about Curecoin, they are currently running testnet for SigmaX a spin off of the new tech developed for Curecoin 2.0. They are currently testing new code for quantum-resistant signatures and mini-blockchain just to name a few features in the new code. If ur interested to know more u can browse https://bitcointalk.org/index.php?topic=603757.3220 just a few pages either side will have you up to date.
March 22, 2016, 07:11:13 PM
Looks like 100mil premine curious what would be the total amount of coins minted for "forging" rewards.
March 22, 2016, 05:48:21 PM
Nice idea, proper marketing, quality presentation -> Moon
https://www.youtube.com/watch?v=Rk_0TjP1gjY
https://www.youtube.com/watch?v=Rk_0TjP1gjY
Its not proper marketing theres no rocket pics, though u did add too da moon.
Didn't know much about Lisk but I can see why the 13.000btc
https://bitcointalksearch.org/topic/annlsk-lisk-blockchain-application-platform-for-javascript-developers-1346646
Tons of info and this "Dust" as well
https://www.youtube.com/watch?v=T6e7lttEFsM
This project might be hand on hand with Ethereum if not better, think I read it already made it to Microsoft Azure and they are not even running the main blockchain yet
What I don't understand is the coin distributions
Supply: 100 million LISK + Forging Rewards (currently 5 LISK per block) and then
How is the distribution?
• 1,000,000 LISK for early supporters (Bounty Campaign).
• 2,000,000 LISK for advisors, partners, and 3rd parties.
• 4,000,000 LISK for campaigns and bounties (after ICO).
• 8,000,000 LISK for the Lisk core team.
• 85,000,000 LISK for ICO participants.
Is this just a massive premine? Glad that Nexus wasn't premined at all
Neither says in specs what is the hashing algorithm they are using, In 2016 security of all these blockchains and cryptos are not a main concern in the future it will be.
March 22, 2016, 08:57:44 AM
Nice idea, proper marketing, quality presentation -> Moon
https://www.youtube.com/watch?v=Rk_0TjP1gjY
https://www.youtube.com/watch?v=Rk_0TjP1gjY
Its not proper marketing theres no rocket pics, though u did add too da moon.
xD
March 22, 2016, 06:59:20 AM
Nice idea, proper marketing, quality presentation -> Moon
https://www.youtube.com/watch?v=Rk_0TjP1gjY
https://www.youtube.com/watch?v=Rk_0TjP1gjY
Its not proper marketing theres no rocket pics, though u did add too da moon.
March 21, 2016, 09:47:03 AM
Nice idea, proper marketing, quality presentation -> Moon
https://www.youtube.com/watch?v=Rk_0TjP1gjY
https://www.youtube.com/watch?v=Rk_0TjP1gjY
March 21, 2016, 09:36:43 AM
we should do Nexus 2.0 ICO
People are mental. LISK...13kBTC
Prism (SCAM) ... 50BTC
Stupidity at the finest.
People are mental. LISK...13kBTC
Prism (SCAM) ... 50BTC
Stupidity at the finest.
March 20, 2016, 10:08:40 PM
Hi guys, I'm still around, running a Nexus node, dropped in to say hello! I will be very busy next few weeks but will try to pop in more often. Cheers, keep up the good work Viz!
March 20, 2016, 01:29:42 PM
Might not be very useful but your wallet is unlocked right?
Yeah, it is/was but thnxs anyway ;-)
The initial debug is just the old directory migration code from coinshield, I'll remove it on next release.
You can run it command line -printtoconsole if you want to see all the full node output including blocks moving through the network, transactions, ect. If you want your daemon to stake you'll need to run it with command line -stake. This is off by default to keep exchanges from staking by accident, so it has to be manually enabled to ensure you want your daemon to stake.
You can verify with the output %%%%%%%%% Daemon Staking Thread Initialized... in your debug.log or daemon console if printing to console is enabled with previously mentioned command.
Thank You,
Viz.
You can run it command line -printtoconsole if you want to see all the full node output including blocks moving through the network, transactions, ect. If you want your daemon to stake you'll need to run it with command line -stake. This is off by default to keep exchanges from staking by accident, so it has to be manually enabled to ensure you want your daemon to stake.
You can verify with the output %%%%%%%%% Daemon Staking Thread Initialized... in your debug.log or daemon console if printing to console is enabled with previously mentioned command.
Thank You,
Viz.
Thnxs Videlicet... it worked, at least I'm seeing the "%%%%%%%%% Daemon Staking Thread Initialized" line, so now I'm waiting to see the stakes come trough...
PS: We miss you all in the IRC channel... Why has it been "dropped"
WhitesoxCrypto
March 20, 2016, 05:54:32 AM
The initial debug is just the old directory migration code from coinshield, I'll remove it on next release.
You can run it command line -printtoconsole if you want to see all the full node output including blocks moving through the network, transactions, ect. If you want your daemon to stake you'll need to run it with command line -stake. This is off by default to keep exchanges from staking by accident, so it has to be manually enabled to ensure you want your daemon to stake.
You can verify with the output %%%%%%%%% Daemon Staking Thread Initialized... in your debug.log or daemon console if printing to console is enabled with previously mentioned command.
Thank You,
Viz.
You can run it command line -printtoconsole if you want to see all the full node output including blocks moving through the network, transactions, ect. If you want your daemon to stake you'll need to run it with command line -stake. This is off by default to keep exchanges from staking by accident, so it has to be manually enabled to ensure you want your daemon to stake.
You can verify with the output %%%%%%%%% Daemon Staking Thread Initialized... in your debug.log or daemon console if printing to console is enabled with previously mentioned command.
Thank You,
Viz.
Jump to: