Topic: . - page 47. (Read 491736 times)
cant wait to see what you have come up with. have you done any testing with the blocknet tech yet.
keep up the great work.
keep up the great work.
Quick update as we have been pretty quiet with the BTC implosion from XT.
5.0 Testing progressing well.
A few key people returning from vacation at the end of the month, at which point we hope to unveil the 'secret project' that has been in the works for the past 6 months.
5.0 Testing progressing well.
A few key people returning from vacation at the end of the month, at which point we hope to unveil the 'secret project' that has been in the works for the past 6 months.
Quick update as we have been pretty quiet with the BTC implosion from XT.
5.0 Testing progressing well.
A few key people returning from vacation at the end of the month, at which point we hope to unveil the 'secret project' that has been in the works for the past 6 months.
5.0 Testing progressing well.
A few key people returning from vacation at the end of the month, at which point we hope to unveil the 'secret project' that has been in the works for the past 6 months.
interesting and so mysterious
Quick update as we have been pretty quiet with the BTC implosion from XT.
5.0 Testing progressing well.
A few key people returning from vacation at the end of the month, at which point we hope to unveil the 'secret project' that has been in the works for the past 6 months.
5.0 Testing progressing well.
A few key people returning from vacation at the end of the month, at which point we hope to unveil the 'secret project' that has been in the works for the past 6 months.
I have started a new hallmark node for more than 2 days but still not been detected.
From my nhz.log, my v4.0e node should have been working properly.
A simple telnet test also shows that connection to my node on port 7774 is successfull, and netstat shows some established connections with other peers.
Is the bounty script still scanning and adding new node(s) regularly?
Anyone from dev team please help, thanks.
From my nhz.log, my v4.0e node should have been working properly.
A simple telnet test also shows that connection to my node on port 7774 is successfull, and netstat shows some established connections with other peers.
Is the bounty script still scanning and adding new node(s) regularly?
Anyone from dev team please help, thanks.
The fact that this is a clon on NXT does not matter too considering many others coins for example, The most important is use of it, A part of it are assets,They need be clear, Transparent and trust, Some peoples were disappointed with a lot of assets not legitimate, but well is it another history. The more important is that distribution finish to see new horizons.
wow , 0.00000037 BTC -11.9%
ye about right for copy and paste coin could go 10 to 20 sats
Well...if it is, it'd be hugely tempting. All I could buy at 20 sats...
wow , 0.00000037 BTC -11.9%
ye about right for copy and paste coin could go 10 to 20 sats
Any comments from devs on this? https://nxtforum.org/index.php?topic=9807.0
yes, full acknowledge to JLs statement.
Please read my answer:
https://nxtforum.org/index.php?topic=9807.msg191864#msg191864
fixed:
old https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v4.0e-revoked
new https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v4.0e
Any comments from devs on this? https://nxtforum.org/index.php?topic=9807.0
yes, full acknowledge to JLs statement.
Please read my answer:
https://nxtforum.org/index.php?topic=9807.msg191864#msg191864
Any comments from devs on this? https://nxtforum.org/index.php?topic=9807.0
Congratulations! Good for you!
Thx a lot. Have celebrated hard *g* posting funny pics.I hope to see it used in some HZ and NXT block explorers etc soon!
You can now post in a new supporters thread, intended
to gather momentum to carry this into the future.
The passphrase generator in the wallets uses a list of 1626 words, which results in 128 bits of entropy. That should be safe for a couple of years already 
Even with lowercase letter-only passwords, more than 55 don't really make sense, as that would give you 256 bits.
The formula is (log2
As long as you use a password manager or the built in generator there's no need to worry.
Even with lowercase letter-only passwords, more than 55 don't really make sense, as that would give you 256 bits.
The formula is (log2
As long as you use a password manager or the built in generator there's no need to worry.
Thank you! Really interesting, The questions of security are always importants.
The passphrase generator in the wallets uses a list of 1626 words, which results in 128 bits of entropy (12 words). That should be safe for a couple of years already
Even with lowercase letter-only passwords, more than 55 don't really make sense, as that would give you 256 bits.
The formula is (log2
As long as you use a password manager or the built in generator there's no need to worry. The problem with brainwallets is humans overestimating the randomness of what they come up with.
Even with lowercase letter-only passwords, more than 55 don't really make sense, as that would give you 256 bits.
The formula is (log2
As long as you use a password manager or the built in generator there's no need to worry. The problem with brainwallets is humans overestimating the randomness of what they come up with.
How many on passphrase letters can be used? I ask it because wallet Hz is too a brainwallet and I want to know how vulnerable is to Brainflayer.
There is a 200K http post data limit.
The 200K limit is only a problem if you want to forge with the account.
In this case the secret must be send to the connected horizon server. Apart from forging the secret is never send to the server and there is no limit except the memory of the computer and browser limits.
Thank you! I had understood that min. are 16 chars,35 chars at least as highly recommended and limit are 100 chars, But if there isn´t limit the
better. The passphrase created by default must be around 70 chars which it´s yet very strong.
How many on passphrase letters can be used? I ask it because wallet Hz is too a brainwallet and I want to know how vulnerable is to Brainflayer.
There is a 200K http post data limit.
The 200K limit is only a problem if you want to forge with the account.
In this case the secret must be send to the connected horizon server. Apart from forging the secret is never send to the server and there is no limit except the memory of the computer and browser limits.
Jump to: