|
opticalcarrier
|
 |
March 10, 2014, 02:07:14 PM |
|
I bring forward a motion for Jean-Luc to modify the NRS client to check string length of the passphrase and reject it if less than 15 characters AND it has zero transactions. (dont want to lock out any people that do have NXT with a 15 char password)
|
|
|
|
|
|
opticalcarrier
|
|
March 10, 2014, 02:08:15 PM |
|
I'm not sure of the exact balances - but yes I do think they were "set aside" and will stay there no matter what happens "with the price".
When you look into the design of TF it certainly favours larger accounts and I don't think that was "by accident".
But the bias is very small, right? I mean, extremely minute, right, by like .0001 or something like that, right? At least this is how I understand it from the other thread where this was discussed. |
|
|
|
|
starik69
Legendary
 Offline
Activity: 1367
Merit: 1000
|
|
March 10, 2014, 02:08:36 PM |
|
|
|
|
|
|
|
opticalcarrier
|
|
March 10, 2014, 02:13:47 PM |
|
Im glad to see TF fully coming to fruition soon. Though to realize its 100% full potential will require all the forgers to begin to lease forging power to accounts that TF forge on public nodes that publish IP address. Otherwise then when its time for an account to forge a block that is not participating with a published IP address for TF, then it cannot receive direct transactions from clients - clients will have to rely on the current broadcast mechanism for their transactions.
And I really wish we could limit effectiveBalance. Not to punish the whales, since they can just lease out their power to different pools. But to actually force a measure of distribution out there.
FTR, Im planning on running a forging account on of the nxtcrypto.org VPSs. I will beef up its CPU/mem, and will see about getting some DDoS protection built in. Will have to shut down API/User interfaces and just leave P2P port open. I will create a vanity account with a very short acct# (currently looking for an 8 digit account, may have to use a 9 digit one) and it will forge with only 1 NXT and everyone can lease out their effectiveBalances to it. Hopefully the other VPS admins out there will do the same thing. Ill work on a HA system for a pair of VPSs that can work together and each can forge with the account if the other is having issues. So hopefully will have a very high uptime % figure.
|
|
|
|
|
|
|
CIYAM
Legendary
Offline
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
|
|
March 10, 2014, 02:20:41 PM |
|
But the bias is very small, right? I mean, extremely minute, right, by like .0001 or something like that, right? At least this is how I understand it from the other thread where this was discussed.
I thought it was higher than that - but I don't have any exact figures (maybe check with the math guy on that). |
|
|
|
redsn0w
Legendary
Offline
Activity: 1778
Merit: 1043
#Free market
|
|
March 10, 2014, 02:21:10 PM |
|
Did you want some TestNxt ?
Please send some to me, if you haven't already. TestNXT to 2299216276842660095 please. Sent 15K TestNxt , enjoy it  . |
|
|
|
|
|
wesleyh
|
|
March 10, 2014, 02:22:50 PM |
|
I bring forward a motion for Jean-Luc to modify the NRS client to check string length of the passphrase and reject it if less than 15 characters AND it has zero transactions. (dont want to lock out any people that do have NXT with a 15 char password)
Here's my new logic for my client http://nxtra.org/nxt-client (to be available later today, not yet uploaded) Start page:  When clicking on the "not registered" link: (first image is only necessary in older browsers, the newest browsers have cryptographically random numbers built in)  Secret phrase is auto generated  User is required to re-type the secret phrase  The user can still choose his own password too...  If you log in with an insecure password, you get a warning  Thoughts? |
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1010
Newbie
|
|
March 10, 2014, 02:23:32 PM |
|
But the bias is very small, right? I mean, extremely minute, right, by like .0001 or something like that, right? At least this is how I understand it from the other thread where this was discussed.
Bias depends on BaseTarget. At some point we'll have to set it in stone and this will define the bias. |
|
|
|
|
|
bitcoinpaul
|
|
March 10, 2014, 02:35:41 PM |
|
This is absolutely great!- Change "register" to "create" (Not an Account yet? Create one) - order and capitalization matters edit: In the future, I would like to see an option for storing the passphrase in a wallet file.
|
|
|
|
|
|
Fatih87SK
|
|
March 10, 2014, 02:36:49 PM |
|
I bring forward a motion for Jean-Luc to modify the NRS client to check string length of the passphrase and reject it if less than 15 characters AND it has zero transactions. (dont want to lock out any people that do have NXT with a 15 char password)
Thoughts? Are those 12 words that will be generated safe enough? Because I see no capitals and no #&(*&!#* or something. |
|
|
|
|
bitcoinpaul
|
|
March 10, 2014, 02:38:34 PM |
|
I bring forward a motion for Jean-Luc to modify the NRS client to check string length of the passphrase and reject it if less than 15 characters AND it has zero transactions. (dont want to lock out any people that do have NXT with a 15 char password)
Thoughts? Are those 12 words that will be generated safe enough? Because I see no capitals and no #&(*&!#* or something. Depends on the size of the dictionary. Wesleyh? |
|
|
|
|
|
wesleyh
|
|
March 10, 2014, 02:38:50 PM |
|
This is absolutely great!- Change "register" to "create" (Not an Account yet? Create one) - order and capitalization matters edit: In the future, I would like to see an option for storing the passphrase in a wallet file. Example of where order and capitalization is wrong? Wallet.dat may be done in the future. |
|
|
|
|
|
wesleyh
|
|
March 10, 2014, 02:39:02 PM |
|
I bring forward a motion for Jean-Luc to modify the NRS client to check string length of the passphrase and reject it if less than 15 characters AND it has zero transactions. (dont want to lock out any people that do have NXT with a 15 char password)
Thoughts? Are those 12 words that will be generated safe enough? Because I see no capitals and no #&(*&!#* or something. Depends on the size of the dictionary. Wesleyh? electrum database. (1626 words) Larger diceware database could also be used.. if that's what the people want. |
|
|
|
|
|
bitcoinpaul
|
|
March 10, 2014, 02:41:13 PM |
|
This is absolutely great!- Change "register" to "create" (Not an Account yet? Create one) - order and capitalization matters edit: In the future, I would like to see an option for storing the passphrase in a wallet file. Example of where order and capitalization is wrong? Wallet.dat may be done in the future. I meant: "their order and capitalization matters |
|
|
|
|
|
bitcoinpaul
|
|
March 10, 2014, 02:41:54 PM |
|
electrum database. (1626 words)
Perfect. |
|
|
|
|
|
Eadeqa
|
|
March 10, 2014, 02:45:29 PM |
|
I bring forward a motion for Jean-Luc to modify the NRS client to check string length of the passphrase and reject it if less than 15 characters AND it has zero transactions. (dont want to lock out any people that do have NXT with a 15 char password)
Here's my new logic for my client http://nxtra.org/nxt-client (to be available later today, not yet uploaded) Start page: Can we get only "Login" and "Register" links here without the field to enter any random password as first option? After clicking "Login" then the user will be able to enter the old password. Also, I think if the user chooses his own password, 35 is way too long. Maybe drop that to 25 |
|
|
|
|
cc001
|
|
March 10, 2014, 02:46:17 PM |
|
electrum database. (1626 words)
Perfect. hm, I'm not sure if that is perfect... 35 random characters (let's say from 50 different characters, numbers and signs) gives 10^59 possibilities. 12 words (or characters) out of 1626 are "only" 10^38 possibilites... |
|
|
|
|
bitcoinpaul
|
|
March 10, 2014, 02:47:08 PM |
|
Let's hear opinions of other experts!
|
|
|
|
|
|
wesleyh
|
|
March 10, 2014, 02:47:28 PM |
|
electrum database. (1626 words)
Perfect. hm, I'm not sure if that is perfect... 35 random characters (let's say from 50 different characters, numbers and signs) gives 10^59 possibilities. 12 words (or characters) out of 1626 are "only" 10^38 possibilites... diceware could be used instead if that's what the people want. More than 7000 in their db. More difficult words though. |
|
|
|
|
|
