Fixed that link to the wallet. Sincere apologies for not taking that one off earlier  |
|
|
|
Yes, it's the same and should start with NXT- (so something like NXT-KTVK-UYXK-W5YK-8C48E) form. The public key issue will be resolved soon because we're going to make it optional. In principle it forced you to announce your public key, but it also makes it much harder for new users to get started... This site should be helpful in activating that account, by the way: http://jnxt.org/key/Thanks. That site got it working. Maybe it should be in the OP? Don't know if this is mentioned elsewhere in the thread, but I've spotted another potential issue from a new user standpoint. When I went to sign into the wallet with my passphrase, I had a small typo and ended up accidentally creating an entirely new wallet. This wasn't immediately obvious (especially as I was expecting the passphrase to be rejected if I entered it incorrectly. If I understand how your brain wallet system works, perhaps it's impossible to avoid this. Unfortunately it's definitely going to lead to people accidentally creating new wallets and then either failing to notice (if zero balance) and potentially sending new funds to the wrong address, or freaking out because they think their funds have vanished or been stolen because they're signed into a different wallet. This isn't intended as a complaint, but as an attempt to help. I work teaching computers and technology to non-technical people and so am always trying to look at technology I'm using from their viewpoint so I can be a better teacher, so stuff like this leaps out at me. Edit: One other thing - I get prompted to update to the new version but then it fails to connect to the update server. Good idea on OP. Will do that later. As to the passphrase: this is integral to what a brainwallet ís. In all actuality the passphrase isn't a "pass" to "unlock" and account at all. In a brainwallet system áll accounts already exist, and the passphrase ís the account. So it's not possible for the system to see if your pass is incorrect, because it's just showing you that actual pass. Ideas welcome, though, as we are aware this is confusing for people who are used to "unlock this file by this pass" ways of doing things. If you like something a bit more "traditional" you can use the MOFO wallet, which does use a wallet.dat system: http://www.mofowallet.com/If you stumble upon a good other way to do this, apart from labelling it full of warnings, let us know.  |
|
|
|
Sup NXTers I have a syncronized supernet wallet on my laptop, is there a way to install the NXT without downloading the blockchain again? What files should I copy over the NXT folder?
Regards
That data is stored in the nxt_db folder. If your Supernet wallet also has such a folder, you can use that |
|
|
|
Hi. I bought some NXT on Bittrex but have no way of withdrawing it.
I installed the client and created an account. I have a public key but I've tried that as well as the account number/ID as the receiving address and Bittrex gives me an error that the address is invalid no matter what I put in the address field.
Any help would be appreciated...
If you post your NXT address and public key here, you'll probably get some NXT, so you don't have to use your public key at Bittrex anymore. Maybe that'll make it easier. Is the address the same as the account ID? There's no mention of an address anywhere in the client and I tried both versions of the ID (formatted with and without hyphens) at Bittrex with no results. Is the idea that the ID/address(?) doesn't work until "activated" by a one-time pairing with the public key during a transaction? Yes, it's the same and should start with NXT- (so something like NXT-KTVK-UYXK-W5YK-8C48E) form. The public key issue will be resolved soon because we're going to make it optional. In principle it forced you to announce your public key, but it also makes it much harder for new users to get started... This site should be helpful in activating that account, by the way: http://jnxt.org/key/ |
|
|
|
Mandatory upgrade to version 1.4.5Update your version before block 330000!NRS 1.4.5 https://nxtforum.org/nrs-releases/nrs-v1-4-5/-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release 1.4.5 https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.4.5.zipsha256: 9292e785c394cb951fc7bf26160137a00896e59764439455abca0da580bb5758 nxt-client-1.4.5.zip Change log: Enable Monetary System at block 330000. This is a hard fork, therefore everybody should upgrade to 1.4.5 or later before that. If upgrading from 1.3.x, read the 1.4.0e and later changelogs for the important changes and new features introduced in the 1.4 series. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJUoBwLAAoJEFOhyXc7+e2A4dMQAPNhZNnbA4UbnD0lt8tg/4Yw mPt3qaRKYnNIregbuGWWvXVU6uEJCDXSaYMhMYV5gZBPZRn6fQWyR5BVqA0kBhBg 9PLuasfJmxCVrrDeJYkB7D2SqxjOrIEJroIYkzuqyFw6u7ZccemXcs+t392XqOS2 CMyZFFtrPSM5mPmyzPPsGj2HsDP8dUNySyUhPvcGn+QgvW3BuFsp4UdJs8GbHsBG 4qQYphH4nYSBGTAm0SoAzNsFYTP/juxFch9bCdXFABVmvYZsaCDeH9fUah6MZkD2 e+nPy102DyfjBjhx8HkwT3OBHnT2fZM0aIf5WJ06L9kL1MdPP0hLPdJz+8YGl+kI ymdRTbRVM0MYWOoNhdhm2m31KNKVysqEO1B1YqyCEDt6P4yeQAl+x/3YjpxQ0pPw cT9QW+X+SLhB88hyazGIlDXTapv3J5DWOTD/mWjvJ6FSm/8I/rpAwBYl6wr6jnUz 5gpT95MyHBrPAhzpvU+GL3ZCpWnOqk29t7AAWlg0E02cAobB8TeZX2R2FJchmBYI +yL88GpC0R+RzMXm/WQchMPlRLDj9JTNTSIoiJZTs5UmdxWsDJcmo4uYfzjGvmCl XjUoTwrT5RtE4dcQDrZi09eldD0PWdxyKwQANOYFWq/frzhnA5t9MO5xfnM9spUx c7CIa1ZwibXB3LZAJ+wU =Q6Qi -----END PGP SIGNATURE-----
|
|
|
|
NEW RELEASE NRS 1.4.4ehttps://nxtforum.org/nrs-releases/nrs-v1-4-4e/-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release 1.4.4e https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.4.4e.zipsha256: fc89bda24de220f173e8b6f88553b51c2eff444b6134a51d79872636003b289d nxt-client-1.4.4e.zip Change log: Improvements and bugfixes in the UI of Monetary System, dividend payments, and account leasing. Added contacts export/import feature. Restrict currency exchange offer sell and buy supply not to exceed total sell and buy limit. This release will force a rescan on testnet only, deleting blocks after 159306. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJUnHBaAAoJEFOhyXc7+e2A4aMQAO++mjoIVSguA62N+wDgh+eR 9l76IeroBeYH/bpzTFxrR5n387qa4YzcitDIhmfN9DNjJqQ/44GFSWZat48n/0ey I0jaBHo6L4VOnaZA7GDRgABuZ0S98QBDAiYFOliQStGVlTwFRXKa/8GHZKFqdw1T Xr9QsH9k3V7N77GmVNl9PpEh85Sn2IjjC2bO5lwpSRkxMPiGEUsg8Y+UML1qve/o I9Y++VdUiLI7KpLFlnXqjuc/qPEy3mrYTN1Fl+Na6/5+4E5yS8NJmwoos7hax3l1 h3PZgzVdptGk5pprzFP5XPRcwevZeR4vC29OYS/Q1Xu+/avZbwjDaZKlDm0eSAhq iuc9y3J9c4OIfeGBsyoplJIQUzRKraONccju8SC/3MlPSHVKFfDWq4S1IpDn+JP2 h4lxD4yARe1XDIwJTxHnI1eqpPuRyeecdcD2wsr5zHNoAIAQ0gJc7W+YrNmind1/ tC84JOA5ubXJ1Br2e0kVWzgXfHuSRjZtK4ErG1PliZIEuBLH970hrbTqH+rnQabq g9t8RLZQ2dAyGzogz6YVR198J/RtWZxs8b1DOIR3Do5t1M7foSTeY6TcTvK6Hd9W AeSyNLsoP2BAXhTE2BRMWEQ6tuCzfXIkKWTok6C0vhBXYRZdPJ5SZGGeQF/YSbqL ec4oCLRQM5CauwHEu4QP =B+iy -----END PGP SIGNATURE-----
|
|
|
|
Funding and a restricted supply. 2014 has taught me there is only so much one can do when you're competing with market demands and crowd funds raising millions. If I could keep things simple Id roll all of NOBL into NOXT, but a lot of people prefer NOBL and dont want a centralized approach. It would be the same as if I hostile took over and forced people into NOXT rather than give them a choice. Because of the burn in a way it is the same coin, you can choose what you prefer.
I líke the option of choice. In the end it is about results, especially for projects like Noblecoin. |
|
|
|
Newbie accounts, please just ignore, move on.
We are very close to the release date for the v1 beta of the client, that is just noise to keep attention away.
Eth.
If that is in reference to myself, well you need to pay closer attention Take BBC seriously, guys, his newbie account here doesn't exactly represent his real status. What, as a cantankerous malcontent? buybitcoinscanada has been around for over 1,5 years. Seems like this account has experienced a hack and deletion of over 1,5 years of posts... Edit: a bit less than 1.5, more like 1 year. I would take posts coming from that account with a huge grain of salt for now. |
|
|
|
I have no idea what a log level is
If I were to guess, I would say he just means: "Please provide more information"  |
|
|
|
NEW RELEASE: NRS v1.4.2e
https://nxtforum.org/nrs-releases/nrs-v1-4-2e/-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release 1.4.2e https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.4.2e.zipsha256: 85d5a5dc18a4ab603657da4cf77d39aa31e723e11971f0cdecf77c128a0ef420 nxt-client-1.4.2e.zip Change log: Additional validations of Monetary System transactions, and bugfixes in existing validations. Allow setting a different file as default page for the API server, in nxt.apiWelcomeFile, default index.html. Bugfixes in processing decimal point conversions in the UI, affecting MS and AE transactions. Bugfixes in currency minting and in MintWorker. The mint dialog has been removed, you can mint using the mint worker utility or manually submit a currencyMint transaction from the test page. Fixed the UI issue of client not responding after submission of certain MS transactions. Fixed duplicate transactions on the dashboard UI issue. The link to the founders table has moved from the currencies table to the transaction info dialog. Other Monetary System UI improvements. Improved peer networking to run the sending of blocks and transactions to peers in a background thread. This release will force a rescan on testnet only, deleting blocks after 159306. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJUltjDAAoJEFOhyXc7+e2AiuUQAJueFgOTx8giUneyE/8iUCfa em38kauWCsAQADmb//JJf80BoYbhl+GN7fCcFh5dBblzLGwsl53nWJK+MlmSOhbz ffwtYOxAEiWEfil2El/AfPZW6Ywwmw8z4qpUclIfgdpA0ps/RNbeXa4hlgG0Hiq3 6EvJftZDgXaR3oJFOf6JXhNmmJW5VKQfF21kqzxt9Vi6E1lZ+EGruaQg/WBzNnD5 W/wg9F9SIxId5OSTo55OVEHxsCL62oMYem0O0A2cf7FtRvJJPXEyg/j4+CQpPF5P hhU8mre/3HzpHfWMjBeIrMk+dMVJ3URCC1nzaEtTAc3+dGGKfcZvWa7q2ugDR20q /zenlx0k+UXYxrdRNKH0blPFofl3GaEpHR/P9njy2sULLUygWwCGerTXMNaXyLZx wnkHDHOhrEjHmtjMEMqfKcc3vuNJPdXg5p/4ulamzrwCdkGUiPftmCJdNB/PNX0T lbN+LcGH/Iz4ZafJbEszcTlGHhGyhkLF8V+vxZfCUg85aNT2rki4HmC9eCzoxNa2 eHMux55+B7xYgv2auUxX9mJyONKqSObp2ohgHaarqFiQU1AxapKWwKlYtmQtG+Ds /qv2bb2PDCYD+bBPtNCaOANhTiFcvKhE/sGJPKQk7BsGAGqqJE3E0FW0uwMjzJq1 aphfIDnxhSmS6JVogeQO =7QnL -----END PGP SIGNATURE-----
|
|
|
|
I don't have the time/energy to fully digest what the paper is saying, but the conclusions of the author seem to say that Nothing at stake is a real problem that hasn't been solved. As we have all the algorithms developed to simulate N@S attack we
present result in the separate paper along with possible ways to resist it.
Giving some results now we present not the full picture of the problem. Fol-
lowing this section it is reasonable to get the impression that this problem
actually matters and we concentrate to possible solutions at the moment....
...The open question for the future work are: (1) the PoS consensus depen-
dence on the measure function (2) the ways to avoid N@S attack if any (3)
the optimal confirmation length investigation (4) the optimal multibranch
depth investigation. Actually, the td;dr version is: - multibranch forging gives measurable possibility to earn more fees. I guess Nxt should not ignore it in long-term as the profitable activity will be implemented by somebody sooner or later
- there's no long-range attack against a blockchain V. Buterin described, only short-range. The short-range attack doesn't allow double-spending but gives multibranching forger possibility to earn more fees in singlebranch environment by producing few blocks in a row. However producing few blocks in a row could be an issue too (e.g. evil forger may postpones orders submissions etc) but not critical at the moment.
- not explicitly stated in the paper but easily derived, a long delay between blocks not only annoying but also a security problem as it's the moment for short-range attack could happens
- we have formally defined nothing-at-stake attack(again, using Buterin's informal definition) and made initial simulations. We haven't included their results in paper as they are seems to be too raw, but I can reveal them here: N@S attack could happens only in short-range, e.g. for within 20 blocks for 10% stake, so with 30 confirmations we haven't observed the successful attack. Also please note the attack has pretty unpredictable nature for attacker, so he can hardly enforce it, even in theory(in practice it's even harder to get it done properly). The correlation with stake size is still the open question, but it's nearly impossible to attack a proof-of-stake currency with "1% stake even" as stated by ButerinSo yes, there máy be problems with certain forms of N@S, and that needs to be researched. Research means keeping an open mind, not cherrypicking and taking out the last sentence and twisting it to mean what you want to mean. They do nót say "Nothing at stake is a real problem that hasn't been solved." They say "We have made a simulation that produces a N@S as described and we are going to find out what it does." |
|
|
|
Nice to see some research on N@S, instead of claims without backup. Would be nice to see some discussion going over this. |
|
|
|
I would like to point everyone to this original research done by Alexander Chepurnoy on PoS and specifically the "Nothing at Stake" problem.
is this kushi? [/quote] Yes, it is. I just felt it was better to use his real name so people can check out his credentials. |
|
|
|
I would like to point everyone to this original research done by Alexander Chepurnoy on PoS and specifically the "Nothing at Stake" problem. For more PoS research articles, please go to http://chepurnoy.org/ and https://github.com/ConsensusResearch Paper on different attacks related to multibranching forging is published by Consensus Research https://github.com/ConsensusResearch/articles-papers/blob/master/multistrategy/multistrategy.pdfTL/DR version and consequences: - multibranch forging gives measurable possibility to earn more fees. I guess Nxt should not ignore it in long-term as the profitable activity will be implemented by somebody sooner or later - there's no long-range attack against a blockchain V. Buterin described, only short-range. The short-range attack doesn't allow double-spending but gives multibranching forger possibility to earn more fees in singlebranch environment by producing few blocks in a row. However producing few blocks in a row could be an issue too (e.g. evil forger may postpones orders submissions etc) but not critical at the moment. - not explicitly stated in the paper but easily derived, a long delay between blocks not only annoying but also a security problem as it's the moment for short-range attack could happens - we have formally defined nothing-at-stake attack(again, using Buterin's informal definition) and made initial simulations. We haven't included their results in paper as they are seems to be too raw, but I can reveal them here: N@S attack could happens only in short-range, e.g. for within 20 blocks for 10% stake, so with 30 confirmations we haven't observed the successful attack. Also please note the attack has pretty unpredictable nature for attacker, so he can hardly enforce it, even in theory(in practice it's even harder to get it done properly). The correlation with stake size is still the open question, but it's nearly impossible to attack a proof-of-stake currency with "1% stake even" as stated by Buterin - the N@S simulation tool is published also https://github.com/ConsensusResearch/MultiBranch so feel free to make your own experiments |
|
|
|
don´t understand Sorry, Daedelus is correct. I was posting and researching a lot about the new feature Monetary Systems that I got it mixed up with you pooling  Apologies for your confusion and congrats on your first forged Nxt |
|
|
|
which way will i obtain profit from lease balance - pool will send me automatically each week ?
With the nxtcrypto pool you need to send a message: To claim your earnings, simply send an AM (can be empty or put whatever you want in there) to the pool account 1460178482 and after this AM has 1440 comfirmations, your confirmed earnings will be sent to you, minus NXT transfer fee. http://pool.nxtcrypto.org/howto.htmlYou can do this easily within your client by sending an empty message to account NXT-K5KL-23DJ-3XLK-22222 (which is account 1460178482) ok, thank so i should send AM before my leasing time time run out or after my leasing period expire Any time is fine. They will send the funds when you want even when your lease time has expired Do remember that it will take 1440 blocks for them to send this, that's about 1,5 days. i already earned 0.01 nxt = it´s 0.0001517263707174008 $ It looks promising Remember that the same with electricity and normal mining, you also have a cost of 1 nxt per minted coin in transaction fees! So you will need to calculate the minting unit well https://bitbucket.org/JeanLucPicard/nxt/issue/207/mint-worker-utilityAdditional Best practices
Never set the isSubmitted flag to true unless you are absolutely sure what's you are doing. You may end up paying a lot of fees and spamming the blockchain.
Always start by minting 1 unit per mint and observe the log messages printed by the mint worker. Look at the hash rate and the number of seconds per transactions. Adjust the nxt.mint.unitsPerMint setting so that the mint worker solves no more than one hash per hour but also consider that a single mint cannot mint more than 1/10000 of the total unit supply. |
|
|
|
UPDATEhttps://nxtforum.org/nrs-releases/nrs-v1-4-1e/-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release 1.4.1e https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.4.1e.zipsha256: 2777a11b701170d7decc01bb82a9049abc37bd293374f852d1810c8195d9842b nxt-client-1.4.1e.zip Change log: This is a bugfix release following 1.4.0e. Fixed Currency Exchange Booth not working. Fixed currency decimals issue. Fixed minor bugs in MS transaction validation. Show total alias count in aliases page. Alias deletion and dividend payment UI fixes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJUkfhFAAoJEFOhyXc7+e2AlyQQAOUQHpZc+03kvf0aVQIy45oU XtHKlt98PwjSKW0MdzyKXXTohdMFTHKR3vvaSRMFqVu+Bvf8ZCL1liLD/J0kidO9 E2AxCvcvAnNKwcNlJQPZjLsboR7aACHG1qwrICOXYeYuBBLrqlUx6UuPjFZdBHXB BszYDcxpIZ8thUwa/dPhTVdq9Q0AmKoPMME/Jq0OH2tfM3SJEMRI4NkWQbQ8YjmB 1xCt8Z2aplKIJGYmo8pvxZBXvo52N277EKXBnZfn55LoHjIQL3hX4WMBc3GwshhA 9mvJNyMsS4ZTRREH2ZjwiVsu2p+sZ53JBzwhXSpzm2R6LoUrrVA9E6h0ZzKWSj/c yFvkZjAvGobmmZ6a1kzAiRGKLildkpS2CIDOyy32NMHL9yu538jbbmMvtVVAr1oM uZehyJxwym+49t0F6dtjwj60nbfYgJoEjXcdidyby+0AQOBHcx+uvhz1easxtsMd 1SgkJ77EdwntK1hXM1Dkx24vA6jABkjihZyBMn3IKQvaSToZFRPe9RXMdqtu+Or6 QmAoXuvy+65I361J6m0wbB1yFvpTgPlOdBAnRr/rx85v3Z+QnNBm6ApmIirINNy7 hRtsvdv6REnI/L8MJdjyGV63nfsuOFqiP32I50cy8XhiO87Cxtpr1SZCHXyk6t5V iO9Z9Cznf748wQC1TW3u =TfLA -----END PGP SIGNATURE-----
|
|
|
|
UPDATEhttps://nxtforum.org/nrs-releases/nrs-v1-4-1e/-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release 1.4.1e https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.4.1e.zipsha256: 2777a11b701170d7decc01bb82a9049abc37bd293374f852d1810c8195d9842b nxt-client-1.4.1e.zip Change log: This is a bugfix release following 1.4.0e. Fixed Currency Exchange Booth not working. Fixed currency decimals issue. Fixed minor bugs in MS transaction validation. Show total alias count in aliases page. Alias deletion and dividend payment UI fixes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJUkfhFAAoJEFOhyXc7+e2AlyQQAOUQHpZc+03kvf0aVQIy45oU XtHKlt98PwjSKW0MdzyKXXTohdMFTHKR3vvaSRMFqVu+Bvf8ZCL1liLD/J0kidO9 E2AxCvcvAnNKwcNlJQPZjLsboR7aACHG1qwrICOXYeYuBBLrqlUx6UuPjFZdBHXB BszYDcxpIZ8thUwa/dPhTVdq9Q0AmKoPMME/Jq0OH2tfM3SJEMRI4NkWQbQ8YjmB 1xCt8Z2aplKIJGYmo8pvxZBXvo52N277EKXBnZfn55LoHjIQL3hX4WMBc3GwshhA 9mvJNyMsS4ZTRREH2ZjwiVsu2p+sZ53JBzwhXSpzm2R6LoUrrVA9E6h0ZzKWSj/c yFvkZjAvGobmmZ6a1kzAiRGKLildkpS2CIDOyy32NMHL9yu538jbbmMvtVVAr1oM uZehyJxwym+49t0F6dtjwj60nbfYgJoEjXcdidyby+0AQOBHcx+uvhz1easxtsMd 1SgkJ77EdwntK1hXM1Dkx24vA6jABkjihZyBMn3IKQvaSToZFRPe9RXMdqtu+Or6 QmAoXuvy+65I361J6m0wbB1yFvpTgPlOdBAnRr/rx85v3Z+QnNBm6ApmIirINNy7 hRtsvdv6REnI/L8MJdjyGV63nfsuOFqiP32I50cy8XhiO87Cxtpr1SZCHXyk6t5V iO9Z9Cznf748wQC1TW3u =TfLA -----END PGP SIGNATURE-----
|
|
|
|
OK, for those confused by "minting" You need to fill out the following in nxt-default.properties file #### MINT #### # Address of the NXT server to which the mint worker submits its transactions (default: localhost) nxt.mint.serverAddress= localhost# Specify a mintable currency code nxt.mint.currencyCode= Coin shortcode# Secret phrase for the minting account, this secret phrase is sent to the host specified by # nxt.mint.serverAddress therefore do not specify secret phrase of an account with lots of funds nxt.mint.secretPhrase= your passphrase# Number of units to mint per transaction # The minting difficulty grows linearly with the number of units per mint nxt.mint.unitsPerMint=1 < no idea exactly what does yet. I left it at 1.# The initial nonce used for minting # Set to 0 to start with a random nonce nxt.mint.initialNonce=0 < left this at 0, too# Number of concurrency threads used for minting # Set to 0 allocate one thread per processor core nxt.mint.threadPoolSize=0 < same# When set to false mint transactions are not submitted when a hash is solved. # Set this value to true to perform actual minting nxt.mint.isSubmitted= trueYou then, with Nxt running, need to run either mint.bat or mint.sh. And voila, you are minting. If anyone can tell us more about the parameters, that would be nice. |
|
|
|
|
Show Posts
