I got Anon136's idea through his paper. Where is BCNext's idea?
https://bitcointalksearch.org/topic/nxt-instant-transactions-with-guaranteed-confirmation-316104
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1664. (Read 2761645 times)
https://bitcointalksearch.org/topic/nxt-instant-transactions-with-guaranteed-confirmation-316104
My peer review:
Reword: However, it solves the problem of determining whose perspective the consensus record should be a reflection of differently
However, it solves the problem of determining whose perspective the consensus record should be a reflection of in a different manner
Reword: In lay-terms, that means that a person who has invested 10billion into mining infrastructure will be able to produce significantly more than 10 times as much hashing power as someone who has invested 1 billion
In lay-terms, that means that a person who has invested 10billion will be able to mine not 10 times more than a person who invested 1billion, but he will mine 100 or maybe even a 1000 times more
Spellcheck: Thus far, it surely seems as if I have been deifying NXT
defying
Spellcheck: it is not in their own interest to horde their own coins. With a little luck these individuals will realize that if they continue to horde their coins,
2x hoard
Do with it what you like. If you don't like it, no problem
Greets
Adding to that, we will also have instant transactions (due to TF); so conceivably, your payment button can be instantly confirmed as well.
That was an idea of Anon136 to use TF for Instant Transactions. BCNext's idea was based on another approach. U can use any or both.
I got Anon136's idea through his paper. Where is BCNext's idea?
Well let's hope so, instant transactions without fast confirmations are not all that useful, I think? But aren't confirmations related to the nr of blocks?
Technically all transfers in the cryptocurrency world are "instant", but we have to wait for confirmations. I assume by Instant Transactions, it actually means instant confirmation.
Adding to that, we will also have instant transactions (due to TF); so conceivably, your payment button can be instantly confirmed as well.
That was an idea of Anon136 to use TF for Instant Transactions. BCNext's idea was based on another approach. U can use any or both.
Ah, I see. Well, the more methods we have to instantly confirm transactions, the better?
Adding to that, we will also have instant transactions (due to TF); so conceivably, your payment button can be instantly confirmed as well.
That was an idea of Anon136 to use TF for Instant Transactions. BCNext's idea was based on another approach. U can use any or both.
I created a pay button for Nxt, thanks to an idea from james (jl777).
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
Great!
I created a pay button for Nxt, thanks to an idea from james (jl777).
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
Very nice!
C-f-b mentioned that in the future, with TF, blocks can be forged with exactly 1 minute in-between each block. Adding to that, we will also have instant transactions (due to TF); so conceivably, your payment button can be instantly confirmed as well.
Well let's hope so, instant transactions without fast confirmations are not all that useful, I think? But aren't confirmations related to the nr of blocks?
Is anyone going to become an NXT/fiat gateway when Asset Exchange is launched? I know about only 1 such case.
We are working on putting a very simple broker type of service were people can buy NXT with EUR.
It will be very very simple and the sole purpose of it is going to be just give "easier" way of buying NXT without going through the hassle of getting btc and then converting.
I hope we will be ready in 1-2 weeks.
We were working to sort out the tax for such a service in Ireland unfortunately for now it seems we will not be able to convince the tax office to not charge VAT on crypto currencies.
I regret to say that the exchange will be postponed until we have clearer statement from the revenue.
I wanted to do it for nxt even with a risk of losing some money but when there are legal issues it becomes even harder..
disappointing!!
Can someone tell me why this server doesn't know which version it's running: http://node4.mynxt.info:7874/update.html
Because you do not allow bot access (in web.xml)
Ok, so I enabled bot access in another one, it knows its own version but can't find out whether there's a newer version out there. Any ideas why?
http://node20.mynxt.info:7874/update.html
Hmm, no, that's weird. Could you modify the update.html and add this:
console.log(this.responseText);
just above
var response = JSON.parse(this.responseText);
in the sendRequest function.
That should tell us more.
Thanks, will do as soon as I get a chance. On my way to the airport now.
Votes are up:(24h)
Best desktop client:
https://bitcointalksearch.org/topic/nxt-reward-program-clients-414965
Best mobile app:
https://bitcointalksearch.org/topic/nxt-reward-program-mobile-apps-clients-414997
Pin
Best desktop client:
https://bitcointalksearch.org/topic/nxt-reward-program-clients-414965
Best mobile app:
https://bitcointalksearch.org/topic/nxt-reward-program-mobile-apps-clients-414997
Pin
I'd like to see a nice-sized bounty on suitably licensed open source code that supports a secure online wallet (similar to blockchain.info's wallet), and actual implementations. There is already a bounty on a high performance implementation of some of the crypto code, but (unless you're running a full NRS instance in Javascript) is such performance required just to send some money, check balances, see recent transactions, create aliases, etc? Especially given that it would be talking to a backend server with a full NRS instance.
There is likely to be huge demand for them. Online wallets are popping up, but they all send the wrong message to users by expecting them to enter his secret phrase.
I created a pay button for Nxt, thanks to an idea from james (jl777).
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
Very nice!
C-f-b mentioned that in the future, with TF, blocks can be forged with exactly 1 minute in-between each block. Adding to that, we will also have instant transactions (due to TF); so conceivably, your payment button can be instantly confirmed as well.
noob question: my tx got only 5 confirmations after a week..is this something to be worry about ?
I created a pay button for Nxt, thanks to an idea from james (jl777).
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
You can test it here: http://nxtra.org/pay-button/
Limitations:
- Currently it's possible that someone else pays at the same time and you get the success message from him.. Of course this is not how it should be ;-) This is an alpha test. I will solve this by either: presenting a dialog where you enter your account ID and then checking that, or waiting for payments with descriptions to be added in NRS so as to identify the unique description.
- It's .. slow. First it has to wait for the next block to be able to confirm your transaction. This can take a long time sometimes. We are not yet at 1 minute a block consistently.
- If you want to wait for more than 1 confirmation, it's going to be slower still. as you will be waiting for x blocks.
Question is: will blocks and confirmations come faster in the future? How fast exactly?
And should I continue developing this? I think it's perhaps wiser to wait until payments with descriptions are out to continue. I could add an account ID entry field tho...
PS: don't mind the QR code, it's not set up properly. The copy address button also doesn't yet work.
Wesley
Anybody selling BELOW dgex for 0.5 BTC?
More and more visits after the Chinese web www.nxts.org constructed,
https://www.dropbox.com/s/gsqouq9sarpdn2m/nxts.jpg
and more and more visitor follow my Chinese twitter weibo.com/nxtcoin
They are now broadcasting Nxt far and far.
Sounds good.
https://www.dropbox.com/s/gsqouq9sarpdn2m/nxts.jpg
and more and more visitor follow my Chinese twitter weibo.com/nxtcoin
They are now broadcasting Nxt far and far.
Sounds good.
Can someone tell me why this server doesn't know which version it's running: http://node4.mynxt.info:7874/update.html
Because you do not allow bot access (in web.xml)
Ok, so I enabled bot access in another one, it knows its own version but can't find out whether there's a newer version out there. Any ideas why?
http://node20.mynxt.info:7874/update.html
Hmm, no, that's weird. Could you modify the update.html and add this:
console.log(this.responseText);
just above
var response = JSON.parse(this.responseText);
in the sendRequest function.
That should tell us more.
Can someone tell me why this server doesn't know which version it's running: http://node4.mynxt.info:7874/update.html
Because you do not allow bot access (in web.xml)
Ok, so I enabled bot access in another one, it knows its own version but can't find out whether there's a newer version out there. Any ideas why?
http://node20.mynxt.info:7874/update.html
Votes are up:(24h)
Best desktop client:
https://bitcointalksearch.org/topic/nxt-reward-program-clients-414965
Best mobile app:
https://bitcointalksearch.org/topic/nxt-reward-program-mobile-apps-clients-414997
Pin
Best desktop client:
https://bitcointalksearch.org/topic/nxt-reward-program-clients-414965
Best mobile app:
https://bitcointalksearch.org/topic/nxt-reward-program-mobile-apps-clients-414997
Pin
Nxt for the whole system, NXT for the token.
Can someone tell me why this server doesn't know which version it's running: http://node4.mynxt.info:7874/update.html
Because you do not allow bot access (in web.xml)
Jump to: