A POS Block-Chain System shouldn't be calling itself a 'COIN'. They're DACs. If I may, I think this is the misconception.. And why some people get so upset and irritated by these 'COIN' launches.. (Steady..). The 'UNIT' running on the POS chain is exactly what the chain says it is,.. a STAKE in the system. POS Systems should rely on making money through the services they provide. NXT's asset exchange, or BitShares in general both provide a utility to their POS network. And that IS worth something. NXT's IPO was exactly that. A sale of shares in a fledgling DAC. I don't think of NXT as coins. They're shares. I had not seen anything like that before. But there hadn't been any pure POS coins until then. Definitely a first for me on both counts. Congratulations most certainly in order..  This is the "Promote the currency or promote the platform" debate  I say both but long term value will come from the platform, as you say, in the AE and other things that are built on top. |
|
|
|
... Already mentioned in another quote above but it seems that he desperately wanted more stakeholders. I wonder why the distribution was cut short then? I understand that he idolized Satoshi but to cut the IPO short just to get a nice round 21 BTC seems a bit excessive.
Nxt got through 2 of the planned 3 month 'IPO' period so, again, 'cut short' has usually been used in the past with no detail to imply that there was a sinister motive to prevent people getting involved Those that did their own research could follow the thread we have been quoting can see anyone had the opportunity to join for around 2 months. Not sure about the Satoshi reference, he at least didn't idolized him overtly. The second or third post in that thread was an edit of a "reserved" post when BCNext went underground after he said someone had contacted him about Nxt, even after he had been careful with his ID and computer IP. It could be true, it could be razamataz. But it isn't important. He liked symbolism and riddles, CfB has said there are hidden references to '1984' in the Nxt algo's as well as the genesis password being the opening line from the same book. 21 was chosen as that was the number of BTC that will ever be. |
|
|
|
It has most of the NXT features but also a adds a few more to distinguish it from its older brother.
Which features does NEM have at the moment? |
|
|
|
If it walks like a duck and quacks like a duck...
...call it a goose as that is what everyone started to refer to it as 12 months later? But it's not a goose in that respect. We weren't using the term IPO or ICO back then, but it was the same thing. How was it different? As discussed above, IPO/ICO are terms used by scammers with the aim of maximizing donations before delivering nothing. Hence all the "never invest in IPOs" by those that got burned. BCNext plan was: The plan was to accumulate users, not money (remember I asked for tiny amounts?)
BCNext never called it an IPO/ICO and asked for donations to be made to a spendable BTC account so he could send the small amounts back if Nxt failed. I don't think there will be decent amount [of Bitcoins], as I said you should send small amounts, it's just for distribution of coins.
Nxt's 'IPO' had far and away the opposite of what most people in crypto today think of. That is the main reason Nxt is referred to as an IPO in my experience, to try and create the same association with the recent IPO scams. Very few know it was the first and less still do their own research. Nxt was capped donations with low funds raised+delivery of ground breaking technology. Most IPOs are raise as much money as possible+deliver nothing. Fun fact: There were over 100 users who expressed an interest and sent tiny amounts to the donation address to be part of the initial Nxt distribution. Only 73 bothered to claim their stakes (eventually, initially I think it was 71). Amusing when you see trolls (no one in here) talking about Nxt as though it was always a sure thing |
|
|
|
Question in the title I feel like I am missing something here.. |
|
|
|
If it walks like a duck and quacks like a duck...
...call it a goose as that is what everyone started to refer to it as 12 months later? |
|
|
|
Just because a lot of people like looking at numbers on screen and attaching significance to them... Someone has converted 300 bitcoins to mgwBTC through Nxt's Multigateway exchange. And now they are trying to convert them all to Nxt   As you can see, they want 9 million NXT in exchange for the BTC. So we may have a new floor price. Or not But there is definitely 300 BTC within Multigateway, currently patiently hoping to become NXTs |
|
|
|
You can only buy such assets with altcoins. You can only buy altcoins with bitcoins.
Not true. You can buy Nxt assets directly with BTC here: http://www.secureae.com/ |
|
|
|
will the technology tree ever be updated?
Devs aren't in charge of the tree website, it's a community project QBTC runs the website, I want to update the tree. I'll try contacting her again. there is defiently room for improvement You can post any comments here: https://nxtforum.org/general-discussion/nxt-technology-tree/ |
|
|
|
|
1.4.8 should give the option to upgrade to the latest version IIRC.
One for Berserk I think
|
|
|
|
IPO/ICO etc didn't exist when Nxt was launched, you won't find anything like that in the launch thread: https://bitcointalk.org/index.php?topic=303898.0Imagine a world where there are only ~35 coins on Coinmarketcap. And most trying to do something for the betterment of crypto. There weren't the users to warrant terms like IPO. You could say Nxt was the first IPO but it would just be a way of showing naivety about the history of Nxt and POS. It is a retrospective label for Nxt, usually intended to try and illicit a negative emotional response in my experience |
|
|
|
what im supose to do with this?
If you are looking for a token backed by a blockchain (100% premined coin) then looked at Nxt's Monetary System. You can create an MSCoin with Nxt in about 3min using the client and it will cost you about 45cents. You can even have a POW distribution if you choose. It is all secured by the Nxt blockchain. Take a look into it, I can answer any questions. |
|
|
|
will the technology tree ever be updated?
Devs aren't in charge of the tree website, it's a community project QBTC runs the website, I want to update the tree. I'll try contacting her again. |
|
|
|
Nxt is the only coin project that constantly delivers what they've promised.
Darn tooting. And we have 18 months of releases to prove it |
|
|
|
Alias System is being used to create a decentralized DNS system (think Namecoin) Anyone interested in promoting Nxt's decentrslized internet, Nxt Hyperboria, to like minded people? Currently an untapped resource of users there Hi guys,
while checking the updates over Hyperboria I just find out that there will be an event called: "Battle of the Mesh v8" from 3rd to 9th August 2015 in Maribor, Slovenia.
Is there any Nxter who is able to attend and spread to them what can Nxt could do or how to integrate the mesh net hardware with the Nxt platform (decentralized DNS)?
That would be awesome and beneficial both for the two communities!!!
|
|
|
|
|
One click installer will be included as standard in all future Nxt releases. Currently on the testnet in version 1.5.
|
|
|
|
Anyone interested in promoting Nxt's decentrslized internet, Nxt Hyperboria, to like minded people? Currently an untapped resource of users there Hi guys,
while checking the updates over Hyperboria I just find out that there will be an event called: "Battle of the Mesh v8" from 3rd to 9th August 2015 in Maribor, Slovenia.
Is there any Nxter who is able to attend and spread to them what can Nxt could do or how to integrate the mesh net hardware with the Nxt platform (decentralized DNS)?
That would be awesome and beneficial both for the two communities!!!
|
|
|
|
New APIs added and tweaks made to pruning. Plain and encrypted messages now prunable in the client UI. Source: https://nxtforum.org/nrs-releases/nrs-v1-5-2eRelease 1.5.2e
*snip*
This is a development release for testing only. Source code is not provided.
Change log:
This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.
Added getAllPrunableMessages API, returning all currently available prunable
messages in reverse block timestamp order.
Added verifyPrunableMessage API, which can be used to verify that a prunable
message obtained from another node (a service provider) matches the hash found
in the blockchain, i.e. has not been tampered with.
Show maxPrunableLifetime setting in getState and getBlockchainStatus. Show
current number of prunable messages in getState.
Changing the nxt.maxPrunableLifetime property now also affects existing
prunable messages (next time pruning is run), as transaction timestamps instead
of expiration timestamps are now used.
Reverted DGS goods delivery maximum size to 10 kbytes, same as in 1.4. For
goods of a larger size, a prunable encrypted message should be included in the
delivery instead.
Removed core restriction on 28 byte minimum prunable message length, this will
be checked by the client UI only.
Added nxt.includeExpiredPrunables property, to be able to force to still
include the prunable parts in the returned transaction JSON, even if expired,
as long as they are still available. Can be used to force an archival node to
always return those, thus allowing another archival node that feeds from it to
also get all of them.
Limit the number of unconfirmed transactions that can be brought in memory to
nxt.maxUnconfirmedTransactions, no limit by default. If set, transactions with
lowest fee/size ratio are dropped from the unconfirmed pool first. The ordering
is same as the one used when selecting which transactions to include in a new
block.
Added requeueUnconfirmedTransactions debug API.
Added support for uncompressed non-prunable encrypted messages and encrypted
to self messages, as a new appendix version, to avoid the need to specify the
compression status as a request parameter when reading them.
Added setLogging API, to allow changing log levels without having to restart
the server.
Added eventRegister and eventWait APIs, to be used for registering listeners
and waiting for server events instead of polling.
Changed the parameters accepted by broadcastTransaction. The prunable parts
must be submitted either in the transactionJSON, or, if using transactionBytes,
in a new prunableAttachmentJSON parameter, which has the same format as the
transaction attachment json. The prunableAttachmentJSON is also returned by
the signTransaction and getTransactionBytes APIs now.
Added support for prunable plain and encrypted messages in the client UI.
Added optional buyer parameter to getDGSGoodsPurchases API.
Voting system UI improvements and bugfixes.
|
|
|
|
Great work guys  On a long enough timeline and given enough adoption, is there a way to prune older transactions themselves and still maintain a secure blockchain? There is a method planned for that too, this is just the first step. |
|
|
|
|
Show Posts
