Hi to all,
I have only few minutes, so I'll make it short.
I'm your average large stakeholder who cannot keep up with the client installations and updateds.
I don't have the time and the tech. knowledge to do that.
I'm not online most of the time for the time being, and this is the reason I said when Nxt started that I'm willing to donate a substantial amount of Nxt to share the burden.
So I'll say it again:
I'm willing to donate more than 3M nxt.
Lets open a fund that will be managed by respectable members that will be able to gurantee that the funds will be spent properly.
For every 2 Nxt that other stakeholders will donate - I'll donate 1 Nxt (3.4M max - already donated 0.4M to bybitcoin and 0.2M privately).
We need a Gavin - someone wants to step forward?
I can create a stakeholders giveaway forum in the nextcoin.org forums |
|
|
|
...bunch of stuff... what was that you said about there not being a contract between you and BCNext? so you can do as you please? Sounds like the same is true of BCNext (since there is not contract and all that jazz) |
|
|
|
Finally managed to have the hallmark done and decoded correctly, after manually encoding all special characters.
I also did this once, and then decided nobody should have to do it manually. So here is a very simple html form one can use to generate hallmark, letting the browser take care of the encoding. No javascript tricks, plain old html. Save this file as nxt/webapps/root/markHost.html and then go to https://localhost:7875/nxt/markHost.html . <html>
<head><title>Generate a Hallmark for your NXT node</title></head>
<body>
<form action="/nxt" method="GET">
<input type="hidden" name="requestType" value="markHost"/>
<table>
<tr>
<td>Public IP:</td>
<td><input type="text" name="host"/></td>
</tr>
<tr>
<td>Weight:</td>
<td><input type="number" name="weight" value="100"/></td>
</tr>
<tr>
<td>Date:</td>
<td><input type="text" name="date" value="2013-12-10"/></td>
</tr>
<tr>
<td>Secret Phrase:</td>
<td><input type="password" name="secretPhrase"/></td>
</tr>
<tr>
<td><input type="submit" value="submit"/></td>
<td></td>
</tr>
</table>
</form>
</body>
</html>
This warning is still valid. I tried to use POST instead of GET, but then I get a NullPointerException. Once this is fixed, the above form should be changed to use POST and the secretPhrase will not appear in the browser history. dude... did you seriously just solve the dynamic IP problem? |
|
|
|
Now time for bad news.
Edit: If stakeholders don't change situation they should sell their coins before price drops below ZERO.
- such DUMP scheme, initiated right now by BCNext, is not good for Nxt. Because those, who believed in the Nxt, and bought some coins at a high price, would loose a lot now. And those, who are bying right now, are not a believers (after such words by BCNext), they are simply very risky traders. if you think about things in terms of cause/effect, its a fantastic idea. in fact, itll even get WORSE. Bravo. |
|
|
|
|
sorry guys it may be something as simple as a mad rush overload - just a bit ago I made a post on another fairly large forum that I frequent about NXT. It may be lots of folks hitting nextcoin from there.
Though unless dgex and nextcoin are ont he same system, it wouldnt explain it.
I guess if we see a mad rush in volume in the next 2 days you'll know who to thank
|
|
|
|
To the other holders who now contribute to bounties or are looking to get involved, it would be nice to have a thread dedicated to these discussions. Having a one stop place for benefactors to see all of the different projects/bounties going on and receive proposals/interface with those looking to start projects would be fantastic and help keep the information organized and simple to find/reference. Anyone want to do this?
Threads with nice velocity already: https://nextcoin.org/index.php?board=8.0Yes, when its all said and done I hope that our moderators/admins/translators over at nextcoin.org will be given some bounty for their efforts. That site is really humming along now |
|
|
|
|
and also, you may want to reconsider allowing the client to be unlocked before having a complete blockchain...
Per the other thread on address length, it appears that if a never-ever-before-been-entered-into-a-client passphrase is entered that results in an already existing visibleAccountId that shares the first 64bits of the full 256bit address with another passphrase, then the client doesnt allow that passphrase.
If you allow clients to unlock before having a complete blockchain, how will you deal with address collision then?
|
|
|
|
|
regarding this hallmark thing, and advertising our actual IP address...
I have DSL that uses PPP. As such my IP will frequently change. My router does have dynamic DNS configured to update my particular DNS name with my IP address after every reboot.
Can I use my DDNS name when I go through the hallmark thing? Will it cause any problems if I never code my IPv4 address?
|
|
|
|
then that first account is notified that the passphrase is unusable?
More like told they just won the jackpot!  O' rly? so you are saying if you randomed satoshi's address you will be very sad and just delete it?  |
|
|
|
then that first account is notified that the passphrase is unusable?
More like told they just won the jackpot! |
|
|
|
can someone who has a reddit account post in the thread http://www.reddit.com/r/CryptoCurrency/comments/1rxtvs/nextcoinorg_new_nxt_forums/cdtuqum and let them know this was never an issue to begin with? The short answer is when a client has a full load of the blockchain, and has a list of all accounts' public keys and addresses, and if a user attempts to create an account with a truly unique passphrase that happens to generate a 256bit account address that shares the same first 64bits with an already-existing account, then that first account is notified that the passphrase is unusable. |
|
|
|
Stable valuation created from dynamic and decentralized adjustment of monetary base. Lol, so it behaves like a real currency instead of a wildly volatile ever appreciating equity hes describing emunie, scheduled to launch in Jan. they are in closed beta now |
|
|
|
Who do I throw my money at and when?
You can throw your money at me now, and I'll deliver just as much hopelessness and despair as they will when you realize you're not getting anything  with just a tiny bit of effort you could deliver even more hopeless and despair. BTC-Market, thats what I call a DEAL. |
|
|
|
So it is all good ?
Yes. CfB *could* have straightened us all out a bit earlier though, instead of letting us all flip the f**k out... |
|
|
|
<lots o awesome shit>
sorry i closed that other thread. thanks for this description. BCNext/CfB: very slick |
|
|
|
I've been reading through the original bitcoin talk thread announcing NXT. As far as I can tell, fundraising was initially announced to be open until the coin launched on Jan 3, but then BCNext closed it without any warning about six weeks earlier than that date after he got 20 BTC ( https://bitcointalk.org/index.php?topic=303898.msg3620732#msg3620732) from only 71 stakeholders even though here he said he wanted at least 250 ( https://bitcointalk.org/index.php?topic=303898.300). I still haven't seen an explanation of why he closed the fundraising so early with so few stakeholders. I'm sure more people would have invested if the window stayed open and that would have reduced the concentration. Does anyone know why this was done? It seems like it would have benefited the coin to keep the fundraising open longer. I missed out by only a few days as well. But I think they ended the stakeholder investor period early so they could launch earlier than emunie. |
|
|
|
Why not? A 20 digit long string of numbers is a perfectly valid visibleID. It corresponds with the visibleID of 1e+58 other accountIDs
Are we all talking past each other here? Are we all even talking about the same thing???
When someone else enters a passphrase that gives already used account they'll see a big red message saying that this account can't be used. Is this a new feature? Also are you talking about only if 2 different passphrases accidentally generate the same account. What about if 2 people use the same passphrase? no hes not talking about 2 different passphrases generating the same private key (because then they share the same public, account, and visible ID) in effect those 2 particular passphrases ARE the SAME EXACT accounts, same thing if 2 people use the same passphrase What we are discussing are results from 2 different sha256(PUBLICKEY) operations where 2 different public keys generate different accountIds but their 1st 64bits are the same |
|
|
|
Why not? A 20 digit long string of numbers is a perfectly valid visibleID. It corresponds with the visibleID of 1e+58 other accountIDs
Are we all talking past each other here? Are we all even talking about the same thing???
When someone else enters a passphrase that gives already used account they'll see a big red message saying that this account can't be used. there has to be something you arent telling us. this doesnt seem possible in our realm. |
|
|
|
They will not see your balance, because the full 256-bits do not match, if I understand. The only issue is that if two accounts share the same first 20 digits, then at that point, if NXT is sent to that address, which account will it go to? Other than the possibility of transactions that are sent to you being "intercepted" by the other address sharing the 20 digits, your balance can't be spent.
Right, so they won't see my balance. So tell me, or CfB, you tell me, I send my 1000 NXT to an address say 11111111111111111111. How does the 'system' know that really I mean to send it to the address with the full key 11111111111111111111999999999999999999999 or the address with the full key 1111111111111111111155555555555555555 Let's say it doesn't and two of us (or more) can log into our own wallets. I have the one ending with the 9s and you have the one ending in the 5s. How does it know that the coins are mine and not yours? How does it stop you spending those coins? The system doesn't know that. But other user won't give u 11111111111111111111 as his account id. Why not? A 20 digit long string of numbers is a perfectly valid visibleID. It corresponds with the visibleID of 1e+58 other accountIDs Are we all talking past each other here? Are we all even talking about the same thing??? |
|
|
|
|
Show Posts
