My suggestions:
a) @all frontend developer: please use finally an unified LOGO, COLORS and FONTS/CSS. As for all business... an corporate design is really important for value of brand recognition and trust!! Maybe the designers should use an unique thread for convention!
You should orientate on the style of info.nxtcrypto.org
The header logo of nxtcrypto.org changed again, why? The current (QTBC) one is an typographic horror!
b) @Admin of forums.nxtcrypto.org: Please find an more readable style as like nextcoin.org. Fonts and colors should be more user-friendly!! Maybe migrate to SMF in reason that the most of the crypto members are familiar with that board software. If you want more traffic on you board, do it. Especially now do you have the chance for get new members in reason of the barefaced business policy of DGEX.
c) @Designers: Someone should write an Corporate Design Manual!
We are working on coordinating to where there is a common look between the info/www/forums sites. A different person manages each one, and they all have other full time jobs. The forums guy has been on vacation. We are working on it. For now can someone please try these modified links to force 2 different styles (other than the green one) https://forums.nxtcrypto.org/index.php?style=1&sid=a80e2a21db06a6e45ca56cbf4c456d59or https://forums.nxtcrypto.org/index.php?style=3&sid=a80e2a21db06a6e45ca56cbf4c456d59Id prefer to keep phpBB it is EXTREMELY more extensible and powerful |
|
|
|
Is there anyway to calculate total amount of darkNXT in existence?
Walk the blockchain, adding up the balances of accounts that don't have an assigned public key? But theoretically I can still send Nxt to an account without a public key, in an offline mode. But that is a good idea, I wonder if Blockchain Explorer can calculate easily. I would prefer that an API be built specifically for this, and that coinmarket cap use the figure of 1billion minus destroyed NXT - darkNXT for its market cap calcs |
|
|
|
CfB + jean-luc + nexern,
There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.
The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?
This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?
James
P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.
i like the idea of a warning and a chance to cancel rather than not allow |
|
|
|
Hey, something strange happened to me today. After I noticed that I seemed to be on a fork (my block did not correspond to the one on the blockexplorer), I copied my blocks.nxt files to a backup location and then deleted them in my client folder. Then I copied a older blockchain in to the folder (from block 29k) but it did not get any new blocks, even after 10 min of waiting and 20+ active peers. I also tried to download from scratch, but no luck, same thing. Just won't download the block chain  Any thoughts what I can do to get the block chain to download? Thanks! when this happens I blow away the whole nxt folder and unzip the latest ver and then copy over a blockchain backup annd restart. sometimes ill reboot. its the only way to be sure (nuke it from orbit) |
|
|
|
Dgex is slow as hell to release funds, but they will be fast as hell to take a huge cut. http://www.nxtchg.com
Dgex alternativewhat are the fees associated there? I cant seem to find any info page on the main site there, just a create account or login links |
|
|
|
P.S.Peercover was willing to invest in all the development, NXT leakage, etc. and be in it for the long term forging revenue model. Actions speak louder than words. Support the company that supports the NXT community.
James - what is the minimum XRP that needs to be in the reserve to trade on Peercover? I just opened a wallet and am unfunded atm. You need 20XRP. Send me your wallet address I will send it to you. You can repay me in NXT in my sig or via ripple send to rfHFcdmZgUKAFVYCaWWfYni6q8H7wLhFXr For those who don't know in ripple you can send NXT or anything to another person and it will automatically show you a selection of what you have in your wallet that would convert to the desired amount James can you give us ripple dummies a quick 1,2,3 step by step of getting USD/EUR/etc into the ripple network to buy XRP? Then I assume it operated like a normal exchange from there? |
|
|
|
Your missing the point about your public key being "published" - this is one of the reasons why address re-use is considered bad.
If someone is able to crack the EC used (with QC I guess) then your funds are gone as they will determine your private key from the public one.
Of course this is also a big problem for Bitcoin - but as this is a 2nd generation crypto-currency I would have thought that this would have been taken into consideration.
What do you mean by EC/QC? But it does sound like you are saying that also with the 2 choices I laid out, that you are saying we need to consider the 3rd choice of sending out your public key and weighing the risk of the curve/sha256 algorithm being cracked itself? so basically weigh 2^64 against the odds of curve/sha256 being broken? how do you even go about devising a key scheme that wouldnt be defeated by QC means? Just not base it on any Curve/ED/etc type of algorithm? |
|
|
|
Your missing the point about your public key being "published" - this is one of the reasons why address re-use is considered bad.
If someone is able to crack the EC used (with QC I guess) then your funds are gone as they will determine your private key from the public one.
Of course this is also a big problem for Bitcoin - but as this is a 2nd generation crypto-currency I would have thought that this would have been taken into consideration.
What do you mean by EC/QC? But it does sound like you are saying that also with the 2 choices I laid out, that you are saying we need to consider the 3rd choice of sending out your public key and weighing the risk of the curve/sha256 algorithm being cracked itself? so basically weigh 2^64 against the odds of curve/sha256 being broken? |
|
|
|
That being said, if you really want to protect yourself, I have outlined some steps here: http://forums.nxtcrypto.org/viewtopic.php?f=17&t=267 Note that this procedure elects to be online to lock in the account, but via a linux live CD. If you want to go the 2^64 route then keep the linux disconnected and then you also dont have to do the full procedure, but note that to be 100% sure here its probably best to not just disco your PC from the internet and do it, especially if you're running windows. Thanks - although if I am understanding this correctly then your public key has been made public when creating the alias or sending 1 NXT. So if the EC is cracked down the track then your NXT would not be safe - so does this mean that by design you cannot store NXT offline safely (meaning safe from some QC that has cracked EC) without better than 2^64 of entropy? I would consider a linux live CD method a safe method to obtain 2^256. even though you do connect to the internet and do account operations, come on, its safe that way. At least for live CDs that were made before NXT. With that fake client that was floating around, anything is possible. You would need to determine which is more safe, the method of not doing account ops on liveCD where the result is 2^64 or the method of the live CD where you do connect and do account ops where the result is 2^256 |
|
|
|
If you send NXT to an address and don't open the address after, no private/public key pair is generated for that address. This means the account is only protected by (if I'm remembering correctly what CfB said) the 64 bits of the account number, not fully protected by all 256 bits of the private key.
Yes - this is what I had recalled - so what I was hoping one could do is to generate the address and somehow publish the public key without the private key (or pass phrase) ever being even temporarily on an online computer. I think I recall him saying that was a yet-to-be-implemented feature. You are right about not ever being official on the blockchain until sending at least 1 NXT to another account, or generating an alias or something else that causes the amount of NXT in the account to go down. Until that transfer happens the address space for the account is only 2^64 and not 2^256. At least for now anyways. But personally I dont think it should ever change, otherwise people will start spamming empty accounts into the blockchain. That being said, if you really want to protect yourself, I have outlined some steps here: http://forums.nxtcrypto.org/viewtopic.php?f=17&t=267 Note that this procedure elects to be online to lock in the account, but via a linux live CD. If you want to go the 2^64 route then keep the linux disconnected and then you also dont have to do the full procedure, but note that to be 100% sure here its probably best to not just disco your PC from the internet and do it, especially if you're running windows. |
|
|
|
|
asking again, in case some night folks have an answer...
I run 9 VPSs, all of them are showing the majority of their hallmarked peers (not all of them, but most) with red flags. Why is this?
I have some 8GB VPSs so set te maxNumberOfConnectedPublicPeers 100 is that too high?
|
|
|
|
|
CfB, can you comment on the probability of upcoming DDOS attacks that tracks in on transparent forging to attack whatever node is scheduled to be the next block generator?
How can we best prepare so that we dont have to learn things the hard way like we all did with the first wave?
|
|
|
|
|
so if i want to run a hatcher on a VPS.... will it require any emunie credentials to be stored on the VPS?
|
|
|
|
everyone please note the www.nxtcrypto.org that has been MUCH improved in the last 2 days. QBTC@nextcoin has worked hard on it and is paying for hosting out of pocket, I hope she gets some bounty for it and to keep it running. I think its in good shape for launch now. As soon as CfB/JLC comes across with the source it will be posted there as well. |
|
|
|
hm, so I think the "shareMyAdress" is set to "true" too?
....mystical...
yes set to true |
|
|
|
I run 9 VPSs, why is it that lots of times, many of them see others as red flags?
What are your values for maxNumberOfConnectedPublicPeers and maxRequestsPerSec in web.xml? 100, 3000 I run 9 VPSs, why is it that lots of times, many of them see others as red flags?
did you set the VPS IP in "myAddress" at web.xml? yes, set to each node's DNS name. I verified that reverse DNS works properly. The hallmarks were generated with the DNS name, not IP address, and hallmarks checked as valid in the admin page tool |
|
|
|
|
I run 9 VPSs, why is it that lots of times, many of them see others as red flags?
|
|
|
|
Yes, but you should check the SHA-256 once you download it. We will start linking to the client announcement post on nxtcrypo.org sites for easy reference back to verify checksum from dev team |
|
|
|
|
Show Posts
