NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

What was the release plan for the decentralized exchange again? I know I read something in here but can't seem to find it.

Stakeholders have not decided yet. Decentralization has some disadvantages.
Last suggestion was to release source code of all basic features on 3rd of January in any case. If no flaws found by the community then launch the exchange (closed source).

[Come-from-Beyond]

Looks like 0.3.15 on my computer can't load blocks. It load blockchain when start up to actual date, and then show "Catching up..." constantly. There are no errors in console.

Delete all nodes in Active peers except blue ones.

[ImmortAlex]

Delete all nodes in Active peers except blue ones.

I have only localhost and 127.0.0.1 except well-known nodes.

[Come-from-Beyond]

Delete all nodes in Active peers except blue ones.

I have only localhost and 127.0.0.1 except well-known nodes.

Do u announce ur IP via "myAddress" in web.xml?

PS: Try https://dl.dropboxusercontent.com/u/67242472/nxtfiles.zip, it contains blockchain at height 10058.

[Sharky444]

Any ETA on build 16? This weekend?

[Come-from-Beyond]

Any ETA on build 16? This weekend?

In 2 days, we need most of peers to update to 0.3.15.

[nelisky]

I'm considering supporting NXT on dividendrippler.com, but I'm still wrapping my head around the protocol and implementation. If you could enlighten me, I'd like to know;

- What's a safe number of confirmations for a transaction to be trusted. I would assume that there being one block per minute, and keeping with bitcoin's 1 hour rule that would be 60 for fair trust level, but for rapid transaction processing (such as in a gambling site) what would be the minimum number of transactions?
- How are fees calculated? There's a 1NXT minimum fee per tx, if I read things correctly, but are there transaction size issues to be worried about? Block size?
- I don't see in the API a way to get the equivalent to the memory pool, a list of transactions waiting inclusion. Can I get that somehow?
- Can I work with raw transactions? I would particularly need to be able to sign transactions "offline".
- Can I create accounts offline? I assume that we're talking about a simple double sha256 of the passphrase so what I'd need to do is create random passphrases and derive the account number from those? Will the network accept sending to any account address or is there any kind of "registration" message that needs to be propagated first?

Thanks in advance!

[ImmortAlex]

Do u announce ur IP via "myAddress" in web.xml?

No.

PS: Try https://dl.dropboxusercontent.com/u/67242472/nxtfiles.zip, it contains blockchain at height 10058.

Doesn't help, I stuck on 10075.

BTW, there's very small number of nodes: 88.198.210.245, 146.185.168.142,    87.230.14.1, nxt.c4c.io, 54.196.0.71, nxt.airdns.org, fluce.airdns.org, 69.146.88.14. That's all.

[Come-from-Beyond]

- What's a safe number of confirmations for a transaction to be trusted. I would assume that there being one block per minute, and keeping with bitcoin's 1 hour rule that would be 60 for fair trust level, but for rapid transaction processing (such as in a gambling site) what would be the minimum number of transactions?

10 Nxt confirmations ~ 1 BTC confirmation. If u send winnings and reference betting transactions (via "referencedTransaction" in "sendMoney" request) then both or none of the transactions will be confirmed (these r so-called chained transactions).

- How are fees calculated? There's a 1NXT minimum fee per tx, if I read things correctly, but are there transaction size issues to be worried about? Block size?

Blocks r limited to 32 KiB. Reference soft takes into account size of transactions when sort them, ordinary payments r always 128 B long.

- I don't see in the API a way to get the equivalent to the memory pool, a list of transactions waiting inclusion. Can I get that somehow?

This is not implemented, post ur request in API thread.

- Can I work with raw transactions? I would particularly need to be able to sign transactions "offline".

U can use "sendMoney" to get a transaction id. Then use "getTransactionBytes" to get raw bytes. Then go online and use "broadcastTransaction" (disabled atm).
In a pseudo-script language this would look like

Code:

broadcastTransaction(getTransactionBytes(sendMoney(transactionData)));

NB: U can broadcast any transactions making other peers to recall them.

- Can I create accounts offline? I assume that we're talking about a simple double sha256 of the passphrase so what I'd need to do is create random passphrases and derive the account number from those? Will the network accept sending to any account address or is there any kind of "registration" message that needs to be propagated first?

Any 64 bit unsinged number can be used as a valid account id. If u need API for converting a passphrase into the account id then post this in API thread.

[Come-from-Beyond]

Do u announce ur IP via "myAddress" in web.xml?

No.

PS: Try https://dl.dropboxusercontent.com/u/67242472/nxtfiles.zip, it contains blockchain at height 10058.

Doesn't help, I stuck on 10075.

BTW, there's very small number of nodes: 88.198.210.245, 146.185.168.142,    87.230.14.1, nxt.c4c.io, 54.196.0.71, nxt.airdns.org, fluce.airdns.org, 69.146.88.14. That's all.

90% of all nodes r zombie nodes controlled by the hacker who helps to test the network.

Try
1. Stop soft.
2. Delete peers.nxt.
3. Start soft.
several times.

Edit: Also remove all well known peers from web.xml except 88.198.210.245.

[abctc]

"Not allowed" is sent if "allowedBotHosts" set.

- I have

Code:

     <param-name>allowedBotHosts</param-name>
     <param-value></param-value>

in my web.xml. Does it set "allowedBotHosts" ?

[Come-from-Beyond]

"Not allowed" is sent if "allowedBotHosts" set.

- I have

Code:

     <param-name>allowedBotHosts</param-name>
     <param-value></param-value>

in my web.xml. Does it set "allowedBotHosts" ?

Put "*" between "><".

[abctc]

Put "*" between "><".

- hmm..  Why I need to do this?   another peer ("Bot") could steal my secret phrase from plain text http request to my server (localhost).

[Come-from-Beyond]

Put "*" between "><".

- hmm..  Why I need to do this?   another peer ("Bot") could steal my secret phrase from plain text http request to my server (localhost).

I'm talking about an asterisk, not ur secret phrase. Or put there ur host u connect from.

[abctc]

I'm talking about an asterisk, not ur secret phrase. Or put there ur host u connect from.

-an asterisk allows to connect any peer, doesn't it ?
I have put 'localhost' there (I connect from the same Win7 computer), it doesn't help to obtain a hallmark, I still receive "Not allowed" response.

[Come-from-Beyond]

I'm talking about an asterisk, not ur secret phrase. Or put there ur host u connect from.

-an asterisk allows to connect any peer, doesn't it ?
I have put 'localhost' there (I connect from the same Win7 computer), it doesn't help to obtain a hallmark, I still receive "Not allowed" response.

I bet ur local host looks like "0:0:0:0:0:0:0:1". Look there.

[abctc]

I bet ur local host looks like "0:0:0:0:0:0:0:1". Look there.

- no, it looks:

Code:

{"host":"127.0.0.1","address":"127.0.0.1"}

[nelisky]

- What's a safe number of confirmations for a transaction to be trusted. I would assume that there being one block per minute, and keeping with bitcoin's 1 hour rule that would be 60 for fair trust level, but for rapid transaction processing (such as in a gambling site) what would be the minimum number of transactions?

10 Nxt confirmations ~ 1 BTC confirmation. If u send winnings and reference betting transactions (via "referencedTransaction" in "sendMoney" request) then both or none of the transactions will be confirmed (these r so-called chained transactions).

chained transactions only prevent part of the problem. The real issue comes from showing bet results too early, allowing the losing bets to be double spent and only the winning ones going through untouched. The effort in BTC terms to orphan an already propagated block are high enough to accept a single confirmation on low value transactions. I'm just trying to get a feel on what would the equivalent be in NXT terms.

- How are fees calculated? There's a 1NXT minimum fee per tx, if I read things correctly, but are there transaction size issues to be worried about? Block size?

Blocks r limited to 32 KiB. Reference soft takes into account size of transactions when sort them, ordinary payments r always 128 B long.

So what does that mean for fees? Is the rule atm a flat  1 NXT per tx?

- I don't see in the API a way to get the equivalent to the memory pool, a list of transactions waiting inclusion. Can I get that somehow?

This is not implemented, post ur request in API thread.

- Can I work with raw transactions? I would particularly need to be able to sign transactions "offline".

U can use "sendMoney" to get a transaction id. Then use "getTransactionBytes" to get raw bytes. Then go online and use "broadcastTransaction" (disabled atm).
In a pseudo-script language this would look like

Code:

broadcastTransaction(getTransactionBytes(sendMoney(transactionData)));

NB: U can broadcast any transactions making other peers to recall them.

What I was aiming for is as much independence from the client as possible, effectively implementing the code elsewhere. Thus creating the transaction using sendMoney would be great *if* I can get an unsigned raw tx, sign it in my code without using the ref client and then ask the client to propagate it. In other words, I need to ask the client for an unsigned transaction and I need to be told how signing is implemented so I can reproduce in my own code. Is any of this already available?

- Can I create accounts offline? I assume that we're talking about a simple double sha256 of the passphrase so what I'd need to do is create random passphrases and derive the account number from those? Will the network accept sending to any account address or is there any kind of "registration" message that needs to be propagated first?

Any 64 bit unsinged number can be used as a valid account id. If u need API for converting a passphrase into the account id then post this in API thread.

I really need a description of the process, not an API. This is yet another thing I must have done without depending on the ref client. Is there any explanation of the algorithm used?

[Come-from-Beyond]

I bet ur local host looks like "0:0:0:0:0:0:0:1". Look there.

- no, it looks:

Code:

{"host":"127.0.0.1","address":"127.0.0.1"}

There we go.

[abctc]

for some strange reason

Code:

     <param-name>allowedBotHosts</param-name>
     <param-value></param-value>

does not allow "localhost" but seems allow "127.0.0.1"