Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on June 29, 2014, 06:33:29 pm

Title: NRS v1.2.0e
Post by: Jean-Luc on June 29, 2014, 06:33:29 pm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.2.0e

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.2.0e.zip

sha256:

a6e3d1c0da1ef80243708352be0509474c7e3afadfb9e6ef25e973e66a2f740c  nxt-client-1.2.0e.zip


This is a development release for testing only. Source code is not provided.


Change log:

This release will run only on testnet. Set nxt.isTestnet=true in nxt.properties.

New features:

Digital goods store.

New http API calls for creating transactions:
dgsListing, dgsDelisting, dgsPriceChange, dgsQuantityChange, dgsPurchase,
dgsDelivery, dgsRefund, dgsFeedback

New http API calls for quering DGS:
getDGSGood, getDGSGoods, getDGSPurchase, getDGSPurchases, getDGSPendingPurchases

Goods and notes exchanged between buyer and seller are encrypted with AES, and
gzip compressed before encryption. Maximum allowed digital goods size is 10240
bytes after compression and encryption.

Alias transfer.

New http API calls: sellAlias, buyAlias

Alias sale can be restricted to a specific buyer, or open to anyone. Alias sale
with price 0 is treated as immediate transfer and doesn't require a separate buy
alias transaction. To change the ask price, submit a new sellAlias transaction.
To cancel a sale, submit a new sellAlias transaction to yourself with price 0.

Buy alias transaction can only be placed if the alias is already for sale. It is
not currently possible to just bid on an alias that is not for sale.

Encrypted messages.
AES encrypted messages are now supported in the core, so there is no need to use
externally encrypted arbitrary messages anymore. Use arbitrary messages only for
plain text, encrypted messages for confidential messaging.

New APIs: sendEncryptedNote and readEncryptedNote. Max message length is 1000
bytes, after compression and encryption.

New http API calls: encryptTo/decryptFrom can be used for encrypting and
decrypting arbitrary text to/from an account. But those just do the encryption
and decryption, don't actually send messages between accounts.

New rsConvert http query for converting account number to RS format and back.

New getBlockId API to get blockId for a given height.

Improved logging, to handle the case when Nxt is embedded as a library.

Minor improvements: getState and getBlockchainStatus now also show application
name, block JSON also shows generatorPublickKey, getAccountId also accepts
publicKey as a parameter.

Updated jetty to version 9.2.1.

Client Updates:

Digital Goods Store UI.

Alias Trading UI.

Encrypted Messages.

Only RS account numbers are allowed. Exchanges and services should switch to RS
format ASAP.

Decode Token Functionality.

Hide Fee / Deadline by default, show via advanced toggle.

Show warning message if user is on a fork (if his account has generated at least
the last 10 blocks).

Several settings (remember passphrase by default, 12/24 hour format).


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJTsFQWAAoJEFOhyXc7+e2AFbYP/3teOdU5PYThxTggarlg85Dn
ycrHFizh5i8ow+uWvTyXp3wfmSsEzUbiF+jeNXeD4n6rITbMbfqgvOp2ISrw09rH
Sp4d16itceurd7XORkzeIHEs0clzYnQlTSurSakFvGZGGwVj5ec3XNty4aJdC+4D
xEgOkfgw8AAqmIM56xtkIEU08RmZODZDWEJHCP4DDDtPw8cZNC91qgYstJ4TEsQi
GZZC10NGAejL6Uyh+sExoKSZS57w6F2x1NNmToPZwBj/oCtWbFvy6TMItoEgrWgc
Qp9adfZyFCmjMjCpde6aLgeRojdE2lPfO4LcqcvkTTqpxH7HC8pYN6E1U5yTTEHh
wKy7UGG7Hj1x2AYsMRsth+Hkm/vYF53YX/9MgWk5viXPM4OBsxtE43cTlIKKohn8
wrGZ0Ca274vgMJFMHRNfQnPfaLiVId1Wd7Hp3Jk1SenxRR8kkzG0hWxZsCTgrc9R
wN/pB06RGFioOC8Y40ryqvXQkvDxL6T2/RobYMZKlHzCdm/QGVSNhhiAqt/XfBjp
WLCdKfC4TGTke+I6PrYuEzwfzPA69vwK+BwYBUJWBphZoAttFjQRoVFMoJLQX2c7
PvYw+vGv5/oz1jJ6cvKKZxaVBTkmMQHJctihme0RmJRytoE80oNSIIaNNL4DyaJ3
ft1UT3zawr9oco4azkTR
=Q/rc
-----END PGP SIGNATURE-----
Title: Re: NRS v1.2.0e
Post by: Berzerk on June 29, 2014, 06:38:28 pm
Wow, thank you so much! :)
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 29, 2014, 06:39:32 pm
Awesome! So fast! I am looking forward to use all the new stuff on testnet!
Title: Re: NRS v1.2.0e
Post by: achim on June 29, 2014, 06:41:11 pm
OMG what an update, such a long list of new features!  :o

Can't wait to test it when I get home! Will the ideenfrische gui be included in the next release?
Title: Re: NRS v1.2.0e
Post by: yassin54 on June 29, 2014, 06:41:26 pm
Thanks Bro. :)
Title: Re: NRS v1.2.0e
Post by: Project2501 on June 29, 2014, 06:42:05 pm
Great job! So many new and useful features!
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 29, 2014, 06:43:00 pm
Quote
Exchanges and services should switch to RS format ASAP.


Damn ... really? ~.~

So the numeric account format is not going to be supported anymore?

edit: solved, thanks: https://nxtforum.org/nrs-releases/nrs-v1-2-0e/msg56109/#msg56109
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 29, 2014, 06:48:53 pm
When I start the run.bat on my windows 7 it closes 0.2 secs later.
Did you set nxt.isTestnet=true in nxt.properties?
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 29, 2014, 06:51:16 pm
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 29, 2014, 06:52:13 pm
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.

Ok thanks, everything is fine then =)
Title: Re: NRS v1.2.0e
Post by: jl777 on June 29, 2014, 06:53:43 pm
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.
I depend on acct # fitting into 64bits
If this is ever changed, it would be a massive amount of work to fix
As long as "indefinitely" means "forever" I am happy about this
Title: Re: NRS v1.2.0e
Post by: TimmyD on June 29, 2014, 06:58:55 pm
Amazing stuff
Title: Re: NRS v1.2.0e
Post by: semibaron on June 29, 2014, 07:06:18 pm
OMG what an update, such a long list of new features!  :o

Can't wait to test it when I get home! Will the ideenfrische gui be included in the next release?

good question
Title: Re: NRS v1.2.0e
Post by: toenu on June 29, 2014, 07:07:08 pm
Wow, thank you so much! :)

Looking for testnet NXT: NXT-GCLL-UXAD-68E5-E5JLV

Me too please:  NXT-XD6V-SDBB-YKYT-FD4RU

This release looks amazing, thank you for your great work devs!

Title: Re: NRS v1.2.0e
Post by: jnsptrsn on June 29, 2014, 07:09:31 pm
Good work!
Title: Re: NRS v1.2.0e
Post by: instacash on June 29, 2014, 07:13:20 pm
Great! If you can please send some testNXT to NXT-LKFM-GQZT-U8TZ-5Z5TS
Title: Re: NRS v1.2.0e
Post by: HolgerD77 on June 29, 2014, 07:20:43 pm
Great job! :-)

When I register an alias, the alias listing row with "edit, transfer, sell" buttons appear for a few seconds (3-5 maybe) and then disappears (tried 3x, e.g. tx 1030169754346291129).
Title: Re: NRS v1.2.0e
Post by: instacash on June 29, 2014, 07:26:44 pm
Will the ideenfrische gui be included in the next release?

I'm wondering about this too. Looking forward :)
Title: Re: NRS v1.2.0e
Post by: devphp on June 29, 2014, 07:30:19 pm
I see there are 'Polls' now too. Qora won't like competition ;)
Title: Re: NRS v1.2.0e
Post by: HolgerD77 on June 29, 2014, 07:31:34 pm
Same disappearing when creating a new poll. Maybe it's because there are not enough peers with the new client yet? If that's generic behaviour in this situation an error/warning message would be nice.
Title: Re: NRS v1.2.0e
Post by: devphp on June 29, 2014, 07:39:34 pm
Hm, isn't delivery automatic in DGS?

I had an idea, if you buy, you get the encrypted product automatically?
Title: Re: NRS v1.2.0e
Post by: Nxter on June 29, 2014, 07:44:57 pm
Thanks for this new awesome features.

I would like to play with them.. Can i get some testNxt: NXT-REN2-VEWP-HR79-32E56

Thank you!!
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 29, 2014, 07:58:35 pm
Hm, isn't delivery automatic in DGS?

I had an idea, if you buy, you get the encrypted product automatically?

Do u know how it could be possible without a 3rd party?
Title: Re: NRS v1.2.0e
Post by: crimi on June 29, 2014, 08:00:07 pm
Need as well some testnet coins: NXT-J5MJ-5YER-WRBT-BCGZF

ty
Title: Re: NRS v1.2.0e
Post by: abctc on June 29, 2014, 08:00:55 pm
Can i get some testNxt: NXT-.................
- ask testNXTs there, please: Some testNXT to test ... (https://nxtforum.org/index.php?topic=119.new#new)

P.S.
Nxt - system (like Bitcoin),
NXT - coin (like BTC).
Title: Re: NRS v1.2.0e
Post by: devphp on June 29, 2014, 08:02:19 pm
Hm, isn't delivery automatic in DGS?

I had an idea, if you buy, you get the encrypted product automatically?

Do u know how it could be possible without a 3rd party?

Why is 3rd party needed?
Seller puts a digital product on sale with the product content stored encrypted on the blockchain.
Buyer purchases this digital product, and gets its contents delivered in an encrypted message automatically right after the purchase. That was my understanding of how it's supposed to work. How does it work then?
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 29, 2014, 08:05:39 pm
Why is 3rd party needed?
Seller puts a digital product on sale with the product content stored encrypted on the blockchain.
Buyer purchases this digital product, and gets its contents delivered in an encrypted message automatically right after the purchase. That was my understanding of how it's supposed to work. How does it work then?

Seller must send the product after a payment. There is no another secure way.
Title: Re: NRS v1.2.0e
Post by: devphp on June 29, 2014, 08:08:20 pm
Seller must send the product after a payment. There is no another secure way.

Yeah, but can this be done automatically, the buy transaction triggers another 'send product data in encrypted message' transaction? I mean, the seller wouldn't have to monitor sales all the time, but just input product data and it's all sent automatically to the buyer.
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 29, 2014, 08:09:31 pm
Yeah, but can this be done automatically, the buy transaction triggers another 'send product data in encrypted message' transaction? I mean, the seller wouldn't have to monitor sales all the time, but just input product data and it's all sent automatically to the buyer.

No.
Title: Re: NRS v1.2.0e
Post by: devphp on June 29, 2014, 08:14:05 pm
Yeah, but can this be done automatically, the buy transaction triggers another 'send product data in encrypted message' transaction? I mean, the seller wouldn't have to monitor sales all the time, but just input product data and it's all sent automatically to the buyer.

No.

That's not so cool :'(
Title: Re: NRS v1.2.0e
Post by: Nxter on June 29, 2014, 08:30:04 pm
how do we vote on a poll?  the link: Vote (todo) does not trigger anything...

Another question: Where can we see and buy the aliases that are for sale?

Thanks.

PS.: I also thought the Digital goods store would be instant and automatic.
Title: Re: NRS v1.2.0e
Post by: devphp on June 29, 2014, 08:31:09 pm
Another question: Where can we see and buy the aliases that are for sale?

If an alias is put on sale, it will show 'buy for X nxts' link when you search for it.
Title: Re: NRS v1.2.0e
Post by: bitcoinpaul on June 29, 2014, 08:37:00 pm
Seller must send the product after a payment. There is no another secure way.

Yeah, but can this be done automatically, the buy transaction triggers another 'send product data in encrypted message' transaction? I mean, the seller wouldn't have to monitor sales all the time, but just input product data and it's all sent automatically to the buyer.

DGS is more like a framework in the core which can be used or developed on.

Btw, the makers of FreeMarket should look into DGS.
Title: Re: NRS v1.2.0e
Post by: PoofKnuckle on June 29, 2014, 08:46:15 pm

Btw, the makers of FreeMarket should look into DGS.

It is being watched.  8)
Title: Re: NRS v1.2.0e
Post by: bitcoinpaul on June 29, 2014, 08:48:16 pm

Btw, the makers of FreeMarket should look into DGS.

It is being watched.  8)

(http://simpsonswiki.com/w/images/thumb/5/5d/Evil_Burns.png/180px-Evil_Burns.png)
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 29, 2014, 08:49:25 pm

Btw, the makers of FreeMarket should look into DGS.

It is being watched.  8)

really looking forward PoofKnuckle!
Title: Re: NRS v1.2.0e
Post by: psic4t on June 29, 2014, 09:08:29 pm
Wow! Thanks for this release!

Can someone send me some Testnxt?

NXT-8V5M-DMD7-JDFZ-E5BQE
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 29, 2014, 09:14:28 pm
1 NXT for listening a product? Awesome!
Title: Re: NRS v1.2.0e
Post by: Isildur23 on June 29, 2014, 09:29:13 pm
Awesome!!!
Title: Re: NRS v1.2.0e
Post by: landomata on June 29, 2014, 09:37:13 pm

(http://simpsonswiki.com/w/images/thumb/5/5d/Evil_Burns.png/180px-Evil_Burns.png)


Nxters...


P.S...I am really trying to get the full implications of DGS & AT  .....@ CFB can't we let AT be the selfless/trustless market hands.

Title: Re: NRS v1.2.0e
Post by: landomata on June 29, 2014, 09:42:01 pm
Hm, isn't delivery automatic in DGS?

I had an idea, if you buy, you get the encrypted product automatically?

Do u know how it could be possible without a 3rd party?

Why is 3rd party needed?
Seller puts a digital product on sale with the product content stored encrypted on the blockchain.
Buyer purchases this digital product, and gets its contents delivered in an encrypted message automatically right after the purchase. That was my understanding of how it's supposed to work. How does it work then?

Can't an AT be the 3rd party....it releases goods once payment is received to a specific account.
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 29, 2014, 09:43:29 pm
AT is completely transparent, I'm afraid it's impossible to use it as a 3rd party for product delivery.
Title: Re: NRS v1.2.0e
Post by: landomata on June 29, 2014, 09:45:46 pm
AT is completely transparent, I'm afraid it's impossible to use it as a 3rd party for product delivery.

Well isn't that why both parties to a transaction can trust it...because it is completely transparent.
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 29, 2014, 09:50:24 pm
Well isn't that why both parties to a transaction can trust it...because it is completely transparent.

How will u hide the product content before the payment is made?
Title: Re: NRS v1.2.0e
Post by: jl777 on June 29, 2014, 09:54:55 pm
Well isn't that why both parties to a transaction can trust it...because it is completely transparent.

How will u hide the product content before the payment is made?
The only way I can think of is to pre-generate encrypted codes for all bidders (active NXT accts?) and implement a first N to redeem them logic.

Maybe there could be a registration step so that an interested bidder requests that an encrypted code is generated to the blockchain. So without needing to bruteforce, all the bidders will know that their encrypted code is there. Some crypto magic to allow each bidder to verify that is indeed the right code, maybe using referenced transactions.

Not sure, but it seems somewhat possible...

James
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 29, 2014, 09:57:51 pm
Not sure, but it seems somewhat possible...

Till now I was sure I had been the most optimistic person on this forum.  :D
Title: Re: NRS v1.2.0e
Post by: jl777 on June 29, 2014, 10:14:59 pm
Not sure, but it seems somewhat possible...

Till now I was sure I had been the most optimistic person on this forum.  :D
i am optimistic that you will figure out how to do this :)
Title: Re: NRS v1.2.0e
Post by: marek3ball on June 29, 2014, 10:48:06 pm
Shouldn't be the price in DGS calculated from USD value based on the current exchange rate and displayed in NXT?

Then the price will be different every time in NXT however from the real world point of view stable price in USD.

testNXT pls: NXT-AWVL-5CB4-PJCH-EX6DY
Title: Re: NRS v1.2.0e
Post by: nxtperceval on June 29, 2014, 11:02:42 pm
This is confusing.Some newbies can download this verison thinkging that is a stable version.
It's not clear enought that only works in testnet.
Title: Re: NRS v1.2.0e
Post by: bitcoinpaul on June 29, 2014, 11:09:31 pm
This is confusing.Some newbies can download this verison thinkging that is a stable version.
It's not clear enought that only works in testnet.

Yeah, reading is hard, I know.
Title: Re: NRS v1.2.0e
Post by: wastedbit on June 30, 2014, 12:04:50 am
NXT Please

NXT-SNH3-N7EH-ACEK-DKBF5

Thanks

Title: Re: NRS v1.2.0e
Post by: rdanneskjoldr on June 30, 2014, 12:09:29 am
Where do alias you put for sale publicly appear??
Title: Re: NRS v1.2.0e
Post by: Pilot on June 30, 2014, 12:50:53 am
Can you send stuff to an account alias? Does the poll system allow for 1 vote per NXT id or is it one vote per NXT in the account?

Won't digital goods bloat the block chain? Or are their plans to checkpoint the block chain more often?
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 30, 2014, 01:06:28 am
Shouldn't be the price in DGS calculated from USD value based on the current exchange rate and displayed in NXT?
The sellers can change prices of goods already listed at any time, they can do it manually (or with a script) if the NXT exchange rate changes significantly. A logic to pull out exchange rates for fiat currencies from an external source doesn't really belong to the core.
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 30, 2014, 01:08:29 am
Where do alias you put for sale publicly appear??
Nowhere. It is like domain names, you search for the specific names you are interested in, and see if they are available, taken, or for sale.
Title: Re: NRS v1.2.0e
Post by: kodtycoon on June 30, 2014, 01:11:11 am
hello, im running nrs ok, says connected etc. but when i go to local host its as if im not running nrs?
Title: Re: NRS v1.2.0e
Post by: joefox on June 30, 2014, 01:14:15 am
hello, im running nrs ok, says connected etc. but when i go to local host its as if im not running nrs?

If you're running the testnet, you need to access it at http://127.0.0.1:6876/ (http://127.0.0.1:6876/)
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 30, 2014, 01:18:47 am
Maybe there could be a registration step so that an interested bidder requests that an encrypted code is generated to the blockchain. So without needing to bruteforce, all the bidders will know that their encrypted code is there. Some crypto magic to allow each bidder to verify that is indeed the right code, maybe using referenced transactions.
Seller needs to encrypt the goods to the specific buyer. How can they do that before knowing who the buyer is going to be? If the goods are stored encrypted on the blockchain, they would need to be decrypted before being encrypted to a particular buyer's public key, for that step seller password is again needed. Also, the goods may not even exist yet - the seller may generate them on demand for each purchase, e.g. if selling coupon codes or software license keys. And they may need to be dependent on additional buyer specific data, e.g. cell phone ID or email, which buyer is required to supply as a note in the purchase transaction.

Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 30, 2014, 01:19:22 am
Can you send stuff to an account alias? Does the poll system allow for 1 vote per NXT id or is it one vote per NXT in the account?
Not sure what you mean by send to an alias. Account aliases are a vanity feature that is not in the core.

The voting system is not ready for testing and will not be part of the stable 1.2 release. I guess Wesley forgot to comment out that code, it is not finished yet.

Quote
Won't digital goods bloat the block chain? Or are their plans to checkpoint the block chain more often?
If they do, we will have to increase the goods listing fees. We don't have blockchain pruning yet.
Title: Re: NRS v1.2.0e
Post by: Pilot on June 30, 2014, 01:26:42 am
Can you send stuff to an account alias? Does the poll system allow for 1 vote per NXT id or is it one vote per NXT in the account?
Not sure what you mean by send to an alias. Account aliases are a vanity feature that is not in the core.

The voting system is not ready for testing and will not be part of the stable 1.2 release. I guess Wesley forgot to comment out that code, it is not finished yet.

Quote
Won't digital goods bloat the block chain? Or are their plans to checkpoint the block chain more often?
If they do, we will have to increase the goods listing fees. We don't have blockchain pruning yet.

What is the allowed size of a digital good? I assume we aren't delivering 1080p video here?
Title: Re: NRS v1.2.0e
Post by: jl777 on June 30, 2014, 01:34:55 am
Maybe there could be a registration step so that an interested bidder requests that an encrypted code is generated to the blockchain. So without needing to bruteforce, all the bidders will know that their encrypted code is there. Some crypto magic to allow each bidder to verify that is indeed the right code, maybe using referenced transactions.
Seller needs to encrypt the goods to the specific buyer. How can they do that before knowing who the buyer is going to be?
This is why I suggested a bidder registration step that prompts the seller to create an encrypted version specifically for the requesting buyer

Quote
Also, the goods may not even exist yet - the seller may generate them on demand for each purchase, e.g. if selling coupon codes or software license keys.
I did not expect this method to work for everything, but it should work for some subset of offerings

Quote
And they may need to be dependent on additional buyer specific data, e.g. cell phone ID or email, which buyer is required to supply as a note in the purchase transaction.
this can be in the buyer's request for encrypted version

I havent figured out all the details yet, but it seems there are two issues:
a) if we store the digital codes in the blockchain, it needs to be encrypted
b) if it is encrypted, then it needs to be specific to the eventual buyer

James
Title: Re: NRS v1.2.0e
Post by: jefdiesel on June 30, 2014, 02:05:46 am
some testnxt please

NXT-GMJR-WL7B-T956-FA4Q9

Title: Re: NRS v1.2.0e
Post by: coolfish on June 30, 2014, 03:07:32 am
Great job! :-)
Title: Re: NRS v1.2.0e
Post by: Evan on June 30, 2014, 03:44:10 am
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.
Why the restriction? I want also the numeric account number.
Title: Re: NRS v1.2.0e
Post by: 2Kool4Skewl on June 30, 2014, 04:40:58 am
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.
Why the restriction? I want also the numeric account number.

The numeric account id does not have any fault tolerance.  It is easier to accidentally send money to a non-existent account if you use the numeric account id.

The Reed-Solomon account id prevents mistyping account ids and is safer to use.
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 04:46:38 am
The Reed-Solomon account id prevents mistyping account ids and is safer to use.

Not only mistyping, but numeric lets user make mistake like  allowing them to send nxt/asset to asset IDs, which is an unknown account that no one controls. One user already lost $1200 by making that error
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 04:50:00 am
It's still not here

http://nxtra.org/nxt-client/

Is there public test node that has accessible  UI?

Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 30, 2014, 05:41:14 am
What is the allowed size of a digital good? I assume we aren't delivering 1080p video here?

10 KiB. Video should be delivered by sending the link.
Title: Re: NRS v1.2.0e
Post by: abctc on June 30, 2014, 05:59:39 am
Quote
Can i get some testNXT .................

- if someone needs testNXTs, just ask them there, please: Some testNXT to test ... (https://nxtforum.org/index.php?topic=119.new#new)
Title: Re: NRS v1.2.0e
Post by: Pilot on June 30, 2014, 06:04:05 am
What is the allowed size of a digital good? I assume we aren't delivering 1080p video here?

10 KiB. Video should be delivered by sending the link.

Ok, but why do I need a blockchain to send a link?
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 30, 2014, 06:29:20 am
Ok, but why do I need a blockchain to send a link?

For privacy the buyer may decide not to provide any other way to contact him.
Title: Re: NRS v1.2.0e
Post by: Evan on June 30, 2014, 07:18:27 am
The Reed-Solomon account id prevents mistyping account ids and is safer to use.

Not only mistyping, but numeric lets user make mistake like  allowing them to send nxt/asset to asset IDs, which is an unknown account that no one controls. One user already lost $1200 by making that error

Can't we have both in the GUI? For example, set the Reed-Solomon account id as the default and one can also configure to use the numeric account id if he likes to and knows what he is doing.
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 07:19:27 am
The Reed-Solomon account id prevents mistyping account ids and is safer to use.

Not only mistyping, but numeric lets user make mistake like  allowing them to send nxt/asset to asset IDs, which is an unknown account that no one controls. One user already lost $1200 by making that error

Can't we have both in the GUI? For example, set the Reed-Solomon account id as the default and one can also configure to use the numeric account id if he likes to and knows what he is doing.

Give me 1 good reason.
Title: Re: NRS v1.2.0e
Post by: stone on June 30, 2014, 07:21:17 am
great.
i want teste it
NXT-SWTX-ETM3-XNGU-GRRH7

thanks.
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 30, 2014, 07:23:14 am
Give me 1 good reason.

Vanity account numbers with 6-digit length.  ;D
Title: Re: NRS v1.2.0e
Post by: LiQio on June 30, 2014, 07:32:38 am
Give me 1 good reason.

Vanity account numbers with 6-digit length.  ;D

or truly beautiful ones even with 9-digit length - please wesleyh allow both ways  :)
Title: Re: NRS v1.2.0e
Post by: Evan on June 30, 2014, 07:36:26 am
Give me 1 good reason.
Well, I don't really have any solid argument for that. Maybe for backward compatibility and give people the right to choose.
Title: Re: NRS v1.2.0e
Post by: instacash on June 30, 2014, 07:43:44 am
Give me 1 good reason.

Vanity account numbers with 6-digit length.  ;D

or truly beautiful ones even with 9-digit length - please wesleyh allow both ways  :)

Agree, I'd also like to have both allowed.
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 07:49:49 am
Sorry, but those are not good reasons. Just for vanity?
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 07:57:52 am
Sorry, but those are not good reasons. Just for vanity?

Agreed. Even if that option is there, it should be disabled by default.
Title: Re: NRS v1.2.0e
Post by: instacash on June 30, 2014, 07:59:02 am
Sorry, but those are not good reasons. Just for vanity?

I like numbers
Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 08:00:42 am
Sorry, but those are not good reasons. Just for vanity?

I like numbers

+1

Why not make RS default, and let the users choose the numeric format in the Settings? Have them see the warning "Are you sure?" and let them choose what they are comfortable with.
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 08:02:40 am
Lol, I don't know why this is even an issue.. It's best if everyone uses the same format.
Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 08:03:18 am
Lol, I don't know why this is even an issue.. It's best if everyone uses the same format.

It's about freedom! :P
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 08:03:34 am
Sorry, but those are not good reasons. Just for vanity?

I like numbers

+1

Why not make RS default, and let the users choose the numeric format in the Settings? Have them see the warning "Are you sure?" and let them choose what they are comfortable with.

Totally disagree. Warning is not enough as people don't read warning and will continue to send money to asset IDs. We lose Nxt users by having it just a "warning"

It needs to be disabled (not just warning) by default


Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 08:04:24 am
Totally disagree. Warning is not enough as people don't read warning and will continue to send money to asset IDs. We lose Nxt users by having it just a "warning"

It needs to be disabled (not just warning) by default

And this is not about freedom :P
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 08:09:29 am
Totally disagree. Warning is not enough as people don't read warning and will continue to send money to asset IDs. We lose Nxt users by having it just a "warning"

It needs to be disabled (not just warning) by default

And this is not about freedom :P

This isn't about "freedom" as you can make your own client or use a different one : )

 It's a usability/safety issue. Given asset IDs are very next to issuer IDS in the client, some people will again make the same mistake and lose money and assets by sending it to asset IDs.

It's the same kind of idiotic design error by previous GUI maker that allowed "blank" password -- which resulted any many users losing money and totally giving up on Nxt.

Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 08:13:19 am
How about putting red letters in bold next to 'Asset id': Do not send funds to Asset id!

And Account and Asset id not one under the other, but on the same line with some space between them, so people see the difference, and the red bold font would make it impossible to make the error of sending to an asset id.

One has to be really drunk to send to an asset id in that case. And if they are drunk, they can make a mistake and send to a wrong account anyway, RS or not RS.
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 08:23:03 am
How about putting red letters in bold next to 'Asset id': Do not send funds to Asset id!

No, thanks. We had a big warning about weak "password" in the previous clients, and you know hhow much money people still lost money by entering a "blank" password?

http://nxtexplorer.com/nxt/nxt.cgi?action=3000&acc=3791936988034107349

Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 08:27:18 am
Here is a problem,

(https://farm4.staticflickr.com/3855/14539568304_deecb8f72d_b.jpg)

Some people are going to send money (and keep sending money) to asset ID. It's right next to account ID

I am pretty sure it will even happen to Nemstake when it's time to redeem and will continue to happen,  unless this thing is corrected by disabling (at least by default) sending money to numeric IDs.
Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 08:29:26 am
I am afraid people will keep losing money because they send to a wrong account. Yes, you can limit the number of these by limiting options for other users, but can't totally exclude this possibility. Most errors are human errors. Well, I can live with the RS only option, not so important, others will get used too, I guess. Just don't make a big deal out of people losing money. It will go on. That's why banks have all these safety measures when they lock your account to keep your money safe, to the point of when you have to fight with them to get it back ;D Hopefully NXT doesn't go that route too much, because when you start limiting options, it's hard to stop.
Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 08:31:19 am
...asset ID. It's right next to account ID

Yeah, why not separate them from each other as far as possible on that page? Red letters in bold font still won't hurt, even if numeric accounts are disabled, just to raise awareness.
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 08:32:23 am
I am afraid people will keep losing money because they send to a wrong account.

However, they will never ever lose money by sending them to account that no one controls (or did control in the past)

Right now a user can send money to accounts that no one controls. That can't happen with RS

Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 08:33:16 am
Right now a user can send money to accounts that no one controls. That can't happen with RS

Alright, you convinced me on that one :)
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 08:35:49 am
...asset ID. It's right next to account ID

Yeah, why not separate them from each other as far as possible on that page? Red letters in bold font still won't hurt, even if numeric accounts are disabled, just to raise awareness.

Yes, good luck in convincing all block explorer and all asset sites to do the same. And why would we go to all that trouble when there is much more effective and easy solution?  That is disable  numeric ID by default.
 




 
Title: Re: NRS v1.2.0e
Post by: xchrix on June 30, 2014, 11:32:23 am
is there somewhere a testnet client online for the public to just login and test it? unfortunately i dont have time right now to install it on my server  :-[
Title: Re: NRS v1.2.0e
Post by: slothbag on June 30, 2014, 12:32:04 pm
Looks great devs!

I am surprised you didn't just integrate the Alias buying and selling directly into the DGS? Keep the alias transfer function, but any buying and selling should just redirect to DGS..

Just my 2 NXT
Title: Re: NRS v1.2.0e
Post by: slothbag on June 30, 2014, 12:59:32 pm
Looks like the API supports cancelling alias sell offers but the GUI doesn't yet, i assume that is going to be added sometime?

Also, it would be great if I try register an alias and the alias is already taken but for sale that I be offered the option to buy it :)
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 30, 2014, 01:03:28 pm
Looks like the API supports cancelling alias sell offers but the GUI doesn't yet, i assume that is going to be added sometime?

Also, it would be great if I try register an alias and the alias is already taken but for sale that I be offered the option to buy it :)

I like it. Offer a buying bid for every Alias. Or maybe if you type in an alias and its already taken you can PM the owner with a price?
Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 01:08:49 pm
@devs,

what's the plan for how long 1.2.0e should run on the test net after nastiest bugs have been found and fixed? One week without major bugs and it goes into production blockchain or longer?
Title: Re: NRS v1.2.0e
Post by: allwelder on June 30, 2014, 02:18:15 pm
what is the max number of goods ?
Title: Re: NRS v1.2.0e
Post by: crimi on June 30, 2014, 02:48:02 pm
I offered 3 items everytime i make a new one, the old ones dissapear (@my products for sale) in the wallet. So i see only one of my products for sale.

I hope i will sell some more moon flights!



Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on June 30, 2014, 03:37:03 pm
Red letters in bold font still won't hurt

For some people they look green...
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 03:38:44 pm
Looks like the API supports cancelling alias sell offers but the GUI doesn't yet, i assume that is going to be added sometime?

Also, it would be great if I try register an alias and the alias is already taken but for sale that I be offered the option to buy it :)

I like it. Offer a buying bid for every Alias. Or maybe if you type in an alias and its already taken you can PM the owner with a price?

Like so? (Will be available in the next beta).

(http://i.imgur.com/kt0ppso.png)

PS: You can cancel an alias sale. There should be a button to do so.

Also fixed some other display issues with alias sale (next version).
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 03:38:59 pm
I offered 3 items everytime i make a new one, the old ones dissapear (@my products for sale) in the wallet. So i see only one of my products for sale.

I hope i will sell some more moon flights!

Cannot replicate this. Anyone else?
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 30, 2014, 03:40:21 pm
Looks like the API supports cancelling alias sell offers but the GUI doesn't yet, i assume that is going to be added sometime?

Also, it would be great if I try register an alias and the alias is already taken but for sale that I be offered the option to buy it :)

I like it. Offer a buying bid for every Alias. Or maybe if you type in an alias and its already taken you can PM the owner with a price?

Like so? (Will be available in the next beta).

(http://i.imgur.com/kt0ppso.png)

PS: You can cancel an alias sale. There should be a button to do so.

Also fixed some other display issues with alias sale (next version).

Nice! =)
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 03:47:52 pm
If it's not for sale a link to the owner is shown, who you can then contact if need be.
Title: Re: NRS v1.2.0e
Post by: Tosch110 on June 30, 2014, 03:50:56 pm
If it's not for sale a link to the owner is shown, who you can then contact if need be.

Sounds like everything for the Alias trading is set up then. Sounds really great!
Title: Re: NRS v1.2.0e
Post by: Jack Needles on June 30, 2014, 04:00:11 pm
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.
Why the restriction? I want also the numeric account number.

I hope numeric account will always be an option.  It is the only way I know my accounts.
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 04:03:21 pm
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.
Why the restriction? I want also the numeric account number.

I hope numeric account will always be an option.  It is the only way I know my accounts.

Start learning your accounts the new way :)
Title: Re: NRS v1.2.0e
Post by: marek3ball on June 30, 2014, 04:38:04 pm
Shouldn't be the price in DGS calculated from USD value based on the current exchange rate and displayed in NXT?
The sellers can change prices of goods already listed at any time, they can do it manually (or with a script) if the NXT exchange rate changes significantly. A logic to pull out exchange rates for fiat currencies from an external source doesn't really belong to the core.
Is it now in development some Web Shop using DGS with automatic price calculation or other advanced features?
Title: Re: NRS v1.2.0e
Post by: devphp on June 30, 2014, 05:33:08 pm
Why would someone need a USD price? Isn't NXT about a paradigm shift? ;)
Title: Re: NRS v1.2.0e
Post by: starik69 on June 30, 2014, 05:59:14 pm
What is discount and why it can be only whole NXT - 1 not 0.1?  ???
Title: Re: NRS v1.2.0e
Post by: wesley on June 30, 2014, 06:16:29 pm
What is discount and why it can be only whole NXT - 1 not 0.1?  ???

Bug, thx!

Discount it what it says, you can give a discount on the official price and that is returned to the buyer.
Title: Re: NRS v1.2.0e
Post by: innovator256 on June 30, 2014, 07:32:07 pm
Its fascinating to see the proof of stake detractors to starting to look at proof of stake voting as an option...here counterparty devs are considering proof of stake voting for DAC functionality :

https://bitcointalk.org/index.php?topic=395761.msg7602706#msg7602706
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 07:42:39 pm
What is discount and why it can be only whole NXT - 1 not 0.1?  ???

Given crypto prices fluctuate so much, no one serious is going to sell stuff in Nxt. That's why services like coinbase are used by Overstock that do auto conversion to US dollars at buy time. 
Title: Re: NRS v1.2.0e
Post by: marek3ball on June 30, 2014, 08:59:35 pm
Why would someone need a USD price? Isn't NXT about a paradigm shift? ;)

As long as we will sell products created in the old world, we will need real time price calculation USD <-> NXT.  8)
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 09:04:02 pm
Why would someone need a USD price? Isn't NXT about a paradigm shift? ;)

As long as we will sell products created in the old world, we will need real time price calculation USD <-> NXT.  8)

It would be even better if prices would auto adjust with Nxt price fluctuation (like happens with coinbase/overstock) , but I guess that isn't possible with blockchain.

From a seller perspective who is not familiar to crypto, he would need clear prices in US dollars so that he knows he isn't losing money by selling as Nxt price fluctuates a week later.

 

Title: Re: NRS v1.2.0e
Post by: prometheus on June 30, 2014, 09:14:11 pm
This webpage is not available

Opera's connection attempt to localhost was rejected. The website may be down, or your network may not be properly configured.

What is this?
Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 09:17:14 pm
When I start the run.bat on my windows 7 it closes 0.2 secs later.
Did you set nxt.isTestnet=true in nxt.properties?

Why isn't it nxt.isTestnet=true by default in this version?

Title: Re: NRS v1.2.0e
Post by: Eadeqa on June 30, 2014, 09:17:39 pm
This webpage is not available

Opera's connection attempt to localhost was rejected. The website may be down, or your network may not be properly configured.

What is this?

Are you trying http://localhost:6876/ ?



Title: Re: NRS v1.2.0e
Post by: msin on June 30, 2014, 09:24:20 pm
In Marketplace, I bought a couple digital goods, it states my orders status as "Pending" under "Purchased Products" but neither order shows up under "My Pending Orders"
Title: Re: NRS v1.2.0e
Post by: marek3ball on June 30, 2014, 09:27:32 pm
Why would someone need a USD price? Isn't NXT about a paradigm shift? ;)

As long as we will sell products created in the old world, we will need real time price calculation USD <-> NXT.  8)

It would be even better if prices would auto adjust with Nxt price fluctuation (like happens with coinbase/overstock) , but I guess that isn't possible with blockchain.

From a seller perspective who is not familiar to crypto, he would need clear prices in US dollars so that he knows he isn't losing money by selling as Nxt price fluctuates a week later.

1) I know price in USD
2) calculate price in NXT (changing every hour)
3) customer will see the NXT price he is paying and underneath small USD price to help understand the value

It looks like DGS will be mainly used through api in e-shops?

Title: Re: NRS v1.2.0e
Post by: msin on June 30, 2014, 09:55:26 pm
In Marketplace, I bought a couple digital goods, it states my orders status as "Pending" under "Purchased Products" but neither order shows up under "My Pending Orders"

Nevermind, I see that "My Pending Orders" is designated for pending orders of items that I'm selling.
Title: Re: NRS v1.2.0e
Post by: starik69 on June 30, 2014, 10:57:49 pm
What is discount and why it can be only whole NXT - 1 not 0.1?  ???

Bug, thx!

Seems the same bug in "new price" field when trying to change price of my product  ::)
Title: Re: NRS v1.2.0e
Post by: joseginxt on June 30, 2014, 11:02:08 pm
Please NXT for test?
NXT-RAWM-5BFS-Y57A-FPH8P
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 30, 2014, 11:25:41 pm
Why isn't it nxt.isTestnet=true by default in this version?
I thought about doing that, but then newbies who just download the latest version without reading the warnings will connect to testnet and start doing transactions with their real accounts. This way only people who know what testnet is and how to enable it can use this version.
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 30, 2014, 11:33:10 pm
@devs,

what's the plan for how long 1.2.0e should run on the test net after nastiest bugs have been found and fixed? One week without major bugs and it goes into production blockchain or longer?
We need to get people to actively test and try to break it, and try the corner cases - purchases not delivered on time should timeout (and the buyer unconfirmed balance updated), sellers changing quantities and prices after a purchase order has been made, multiple buyers making orders exceeding total available quantity, and so on. Similar to what we did when testing AE.

Then with a stable release that can run on main net, a milestone block will be set at which DGS, alias transfer, and encrypted messages will become active, at least a week in the future, and within that time everyone - including exchanges and websites - should upgrade to the 1.2 stable release.
 
Title: Re: NRS v1.2.0e
Post by: Berzerk on June 30, 2014, 11:36:51 pm
Wesley: I can't search for the tags.
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on June 30, 2014, 11:43:57 pm
Indexing and searching tags is not planned to be done in the client for now. One day I may add server side lucene search, but this is after 1.3 for sure. Right now tags should be used by external services, like the block explorers, to index and allow searching the goods.
Title: Re: NRS v1.2.0e
Post by: Berzerk on June 30, 2014, 11:48:57 pm
Indexing and searching tags is not planned to be done in the client for now. One day I may add server side lucene search, but this is after 1.3 for sure. Right now tags should be used by external services, like the block explorers, to index and allow searching the goods.


Okay. It's not needed. Here have your 100th applaud! :)
Title: Re: NRS v1.2.0e
Post by: MyZhre on July 01, 2014, 12:21:46 am
Client side bug: can not change price to fractions, "PriceNXT is invalid."
Title: Re: NRS v1.2.0e
Post by: joefox on July 01, 2014, 12:41:09 am
Client side bug: can not change price to fractions, "PriceNXT is invalid."

I have the same problem when trying to apply discounts to goods in order's I'm filling -- only whole numbers, up to the price of the good, are accepted.
Title: Re: NRS v1.2.0e
Post by: TeamWealth on July 01, 2014, 05:00:34 am
Well i guess no one wants my clearly 100% legit nigerian 1TB solid state drives which come preloaded with a guranteed!!!!!!!!! Non compromised NRS Client! Order today! Only .01 NXT.


And a bit more serious, Could we get the available supply posted somewhere on the marketplace? Or am i just blind and don't see it?

And could the advanced options be a toggle so if you click it again then the "advanced" options disappear?


Other then that, i haven't really encountered any bugs through my limited testing that have not already been spoken of earlier on in this thread.
Title: Re: NRS v1.2.0e
Post by: slothbag on July 01, 2014, 06:36:53 am
Well i guess no one wants my clearly 100% legit nigerian 1TB solid state drives which come preloaded with a guranteed!!!!!!!!! Non compromised NRS Client! Order today! Only .01 NXT.

Seems legit.. bought one :)

So the encrypted messages features is awesome, and i want to start using it.. but at 6c per message it can really start to add up.. i'll always be thinking its cheaper to use other messaging apps.. gchat, whatsapp, skype are all free.. Do you think the fee will drop at some point?
Title: Re: NRS v1.2.0e
Post by: slothbag on July 01, 2014, 06:39:17 am
Concern regarding MarketPlace.. so if you purchase things with marketplace the digital goods are encrypted to your private key.. so if your key gets compromised not only do you loose your nxt, but also any products / keys that you may have ordered.

Sounds dangerous
Title: Re: NRS v1.2.0e
Post by: 2Kool4Skewl on July 01, 2014, 06:56:03 am
Well i guess no one wants my clearly 100% legit nigerian 1TB solid state drives which come preloaded with a guranteed!!!!!!!!! Non compromised NRS Client! Order today! Only .01 NXT.

Seems legit.. bought one :)

So the encrypted messages features is awesome, and i want to start using it.. but at 6c per message it can really start to add up.. i'll always be thinking its cheaper to use other messaging apps.. gchat, whatsapp, skype are all free.. Do you think the fee will drop at some point?

The fee is scheduled to drop to 0.1 NXT after 1 NXT is over 10 cents.
Title: Re: NRS v1.2.0e
Post by: devphp on July 01, 2014, 06:59:28 am
Do you think the fee will drop at some point?

https://nxtforum.org/nrs-releases/nrs-v1-1-4/msg43485/#msg43485
Title: Re: NRS v1.2.0e
Post by: wesley on July 01, 2014, 07:00:42 am
Well i guess no one wants my clearly 100% legit nigerian 1TB solid state drives which come preloaded with a guranteed!!!!!!!!! Non compromised NRS Client! Order today! Only .01 NXT.

Seems legit.. bought one :)

So the encrypted messages features is awesome, and i want to start using it.. but at 6c per message it can really start to add up.. i'll always be thinking its cheaper to use other messaging apps.. gchat, whatsapp, skype are all free.. Do you think the fee will drop at some point?

The fee is scheduled to drop to 0.1 NXT after 1 NXT is over 10 cents.

No, after DB migration is done.
Title: Re: NRS v1.2.0e
Post by: devphp on July 01, 2014, 07:03:08 am
Concern regarding MarketPlace.. so if you purchase things with marketplace the digital goods are encrypted to your private key.. so if your key gets compromised not only do you loose your nxt, but also any products / keys that you may have ordered.

Sounds dangerous

At some point in the future it would be nice to have a 'Transfer my purchased goods to another account' feature, like the 'Transfer asset' feature, if it's possible.
Title: Re: NRS v1.2.0e
Post by: furball on July 01, 2014, 08:32:20 am
I know this is mostly about the DGS etc, but just wondering are there any plans to include a "List all assets" feature in the AE section rather than having to search asset id's elsewhere?
Title: Re: NRS v1.2.0e
Post by: Come-from-Beyond on July 01, 2014, 08:34:06 am
I know this is mostly about the DGS etc, but just wondering are there any plans to include a "List all assets" feature in the AE section rather than having to search asset id's elsewhere?

Try https://nxtblocks.info/#section/assets_exchange
Title: Re: NRS v1.2.0e
Post by: LocoMB on July 01, 2014, 08:50:16 am
I saw the details about this only just now because I have been digging into bitcoin wallet features for the last days.
Now I saw that numerical account IDs are to be dropped in 1.2

IMO, RS is nothing but some stupid and superfluous sometimes useful memnonic sugar coating, which is why I don't like it. which is useful for human operators, but not for automated handling.

So it is the right thing to go go the extra mile and include it.

And what is the API call used for to convert these two formats?
Looks like I have to read up on this thread, which I have not been able to do yet.

New rsConvert http query for converting account number to RS format and back.


Quote
edit: solved, thanks: https://nxtforum.org/nrs-releases/nrs-v1-2-0e/msg56109/#msg56109
[\quote]
Title: Re: NRS v1.2.0e
Post by: wesley on July 01, 2014, 08:52:52 am
I just got some news about numerical account IDs to be dropped in 1.2

- please anybody, where can I find out more about this?
Has there been a discussion that I have missed?
IMO, RS is nothing but some stupid and superfluous memnonic sugar coating, which is why I don't like it.

Is there a reason to switch to that exclusively, other than prevent Joe Sixpack from making typos and complaining?

Bold is the reason.

Numeric id's still work in the API, forever. It's just not displayed in the client any more.
Title: Re: NRS v1.2.0e
Post by: LocoMB on July 01, 2014, 08:55:37 am
yes because otherwise an api call to convert these two would make no sense at all.

How about a timetable for transition from testNet to mainNet for 1.2??
Title: Re: NRS v1.2.0e
Post by: slothbag on July 01, 2014, 10:38:54 am
No, after DB migration is done.

Is there anywhere to see the current features being worked on? and maybe a little blurb about them?  If there isn't i'm happy to invest some time into putting something together.
Title: Re: NRS v1.2.0e
Post by: wesley on July 01, 2014, 10:56:43 am
No, after DB migration is done.

Is there anywhere to see the current features being worked on? and maybe a little blurb about them?  If there isn't i'm happy to invest some time into putting something together.

Monetary system and voting system are next on the list. Although there is no official "list" :)
Title: Re: NRS v1.2.0e
Post by: starik69 on July 01, 2014, 11:30:16 am
Same bug (only whole NXT) in refund field when trying to refund  ::)
Title: Re: NRS v1.2.0e
Post by: Eadeqa on July 01, 2014, 06:44:07 pm

Is there a reason to switch to that exclusively, other than prevent Joe Sixpack from making typos and complaining?

Bold is the reason.

It's not just "typo". It also prevents users from sending money/assets to asset IDs, which are valid Nxt accounts, even though no one controls them,
Title: Re: NRS v1.2.0e
Post by: Pilot on July 01, 2014, 07:28:35 pm
Well i guess no one wants my clearly 100% legit nigerian 1TB solid state drives which come preloaded with a guranteed!!!!!!!!! Non compromised NRS Client! Order today! Only .01 NXT.

Seems legit.. bought one :)

So the encrypted messages features is awesome, and i want to start using it.. but at 6c per message it can really start to add up.. i'll always be thinking its cheaper to use other messaging apps.. gchat, whatsapp, skype are all free.. Do you think the fee will drop at some point?

Yes, I always wondered why the fees weren't different depending on transaction type. For example, the fee to send a message should be much less than the fee to transfer an asset/alias which should be less than the fee to send NXT which should be less than the fee to create an asset, etc.
Title: Re: NRS v1.2.0e
Post by: Pilot on July 01, 2014, 07:30:14 pm
I saw the details about this only just now because I have been digging into bitcoin wallet features for the last days.
Now I saw that numerical account IDs are to be dropped in 1.2
IMO, RS is nothing but some stupid and superfluous memnonic sugar coating, which is why I don't like it.

Is there a reason to switch to that exclusively, other than prevent Joe Sixpack from making typos and complaining?

Yes, because it has a checksum.

Is there good reason to NOT switch?
Title: Re: NRS v1.2.0e
Post by: LocoMB on July 01, 2014, 07:32:22 pm


I am just updating my Api implementation - can anybody confirm to me that these have been dropped in 1.2.0 ?

Wesley or maybe JL?


DOes anybody have an idea on the time when 1.2.0e will switch to mainNet?

Thanks!


  getAliasURI
 
  listAccountAliases
 
 getAssetsByName
 
 assignAlias
 
 getAliasId
       
 getAliasIds
       
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 01, 2014, 07:54:41 pm


I am just updating my Api implementation - can anybody confirm to me that these have been dropped in 1.2.0 ?

Wesley or maybe JL?


DOes anybody have an idea on the time when 1.2.0e will switch to mainNet?

Thanks!


  getAliasURI
 
  listAccountAliases
 
 getAssetsByName
 
 assignAlias
 
 getAliasId
       
 getAliasIds
     

The API changes are not new, see 1.1.4 changelog:

Aliases http API cleanup. There are only two API requests to get aliases now:

getAlias
parameters: either "aliasName" (the alias name) or "alias" (the alias id)
returns: full Alias JSON

getAliases
parameters: "timestamp" (optional timestamp) and "account" (the account id,
required)
returns: list of aliases (full JSON) owned by the account, optionally filtered
by timestamp

The old getAliasId, getAliasIds, getAliasURI and listAccountAliases have been
removed as they are redundant and the new requests return all necessary info.

assignAlias has been renamed to setAlias, with "aliasName" and "aliasURI"
parameters.

Removed getAssetsByName API.

The getAssetsByIssuer API now accepts a multivalued "account" parameter and
returns a list of lists of assets issued by those accounts.


No, I don't know when 1.2.0e will be ready for main net. Some time this month.
Title: Re: NRS v1.2.0e
Post by: jl777 on July 01, 2014, 08:02:29 pm
I saw the details about this only just now because I have been digging into bitcoin wallet features for the last days.
Now I saw that numerical account IDs are to be dropped in 1.2
IMO, RS is nothing but some stupid and superfluous memnonic sugar coating, which is why I don't like it.

Is there a reason to switch to that exclusively, other than prevent Joe Sixpack from making typos and complaining?

Yes, because it has a checksum.

Is there good reason to NOT switch?
Internal to software numeric fits in 64 bits, this is VERY handy and makes the code a lot more efficient.
Also, software doesnt make typos (if it did your hardware is failing)
Title: Re: NRS v1.2.0e
Post by: jl777 on July 01, 2014, 08:04:07 pm


I am just updating my Api implementation - can anybody confirm to me that these have been dropped in 1.2.0 ?

Wesley or maybe JL?


DOes anybody have an idea on the time when 1.2.0e will switch to mainNet?

Thanks!


  getAliasURI
 
  listAccountAliases
 
 getAssetsByName
 
 assignAlias
 
 getAliasId
       
 getAliasIds
     

The API changes are not new, see 1.1.4 changelog:

Aliases http API cleanup. There are only two API requests to get aliases now:

getAlias
parameters: either "aliasName" (the alias name) or "alias" (the alias id)
returns: full Alias JSON

getAliases
parameters: "timestamp" (optional timestamp) and "account" (the account id,
required)
returns: list of aliases (full JSON) owned by the account, optionally filtered
by timestamp

The old getAliasId, getAliasIds, getAliasURI and listAccountAliases have been
removed as they are redundant and the new requests return all necessary info.

assignAlias has been renamed to setAlias, with "aliasName" and "aliasURI"
parameters.

Removed getAssetsByName API.

The getAssetsByIssuer API now accepts a multivalued "account" parameter and
returns a list of lists of assets issued by those accounts.


No, I don't know when 1.2.0e will be ready for main net. Some time this month.
I also noticed that getAccountId API doesnt have "accountId" field anymore, it was changed to "account"
I dont mind putting in an if statement depending on version, but any benefit to changing "accountId" to "account"?
Title: Re: NRS v1.2.0e
Post by: Eadeqa on July 01, 2014, 08:05:48 pm
Internal to software numeric fits in 64 bits, this is VERY handy and makes the code a lot more efficient.
Also, software doesnt make typos (if it did your hardware is failing)

No one ever said that internal software was about to change, so what's your point?
Title: Re: NRS v1.2.0e
Post by: slothbag on July 01, 2014, 11:43:15 pm
I'd like to be able to add a product into the MarketPlace without a set price, then the purchaser can click purchase and no funds are sent.. that way I can calculate the cost depending on the order specific.
Title: Re: NRS v1.2.0e
Post by: PoofKnuckle on July 02, 2014, 12:41:19 am
Is there any place where I can find an explanation of the DGS APIs?

I am trying them out using this URL: http://localhost:6876/test

But I see somethings that I can't figure out, and I don't see them reflected in the UI. For instance, in this API:

dgsListing

There are these two fields at the bottom:

referencedTransactionFullHash
broadcast

I have no idea what they do.

Title: Re: NRS v1.2.0e
Post by: jl777 on July 02, 2014, 02:03:26 am
Is there any place where I can find an explanation of the DGS APIs?

I am trying them out using this URL: http://localhost:6876/test

But I see somethings that I can't figure out, and I don't see them reflected in the UI. For instance, in this API:

dgsListing

There are these two fields at the bottom:

referencedTransactionFullHash
broadcast

I have no idea what they do.
those are the same for a lot of API calls
referencedTransactionFullHash is if it requires another tx to be in the blockchain, just leave it blank for normal use
broadcast is if you want to generate tx bytes without it going to the network, just leave it blank for normal use
Title: Re: NRS v1.2.0e
Post by: renat0 on July 02, 2014, 06:50:28 am
No, after DB migration is done.

Is there anywhere to see the current features being worked on? and maybe a little blurb about them?  If there isn't i'm happy to invest some time into putting something together.

Monetary system and voting system are next on the list. Although there is no official "list" :)
So glad to know we got developers that are never satisfied. This is what makes us stronger and nxt #1 without doubts. Never grow satisfied my friends! Let us always improve and get better!
Thank you very much for your hard work! You and everyone else who makes nxt #1!
Title: Re: NRS v1.2.0e
Post by: apenzl on July 02, 2014, 08:27:52 am
+1440
Title: Re: NRS v1.2.0e
Post by: LocoMB on July 02, 2014, 09:23:48 am
I am proud to announce that nxtPowertools now provides access to the FULL NRS1.2.0e api (85 calls)  ;D

github.com/l8orre/nxtPwt/tree/master/nxtPwt

I will make some more noises about this later on - Klappern gehört zum Handwerk!
This really shows the power of python, and how nice it is to have such a modular approach!
 
Title: Re: NRS v1.2.0e
Post by: Tosch110 on July 02, 2014, 02:46:45 pm
@wesley, will the client default also upgraded then?

Right now we have 'Account Balance' - 'Forged Balance' - 'Assets Owned' and 'NRS Version'

Can that be updated to the needs of the standard user like:

'Account Balance' - 'Assets Owned' - 'DGS Items' and 'Aliases' maybe?

A link that is either red or green with the current version of NRS below would be sufficient I think.
Also the forged amount display can be put into the Blocks or somewhere else for 'big holders' that are interested in this statistics.
Title: Re: NRS v1.2.0e
Post by: sile16 on July 03, 2014, 03:09:11 am
Can someone send me some testnet NXT ?

NXT-CMCA-6HB6-PYCF-FYF4D

Thanks!
Title: Re: NRS v1.2.0e
Post by: coolfish on July 03, 2014, 03:26:12 am
Maybe clients should support some of the labels code

Eg. 
Code: [Select]
[img][/img]
[url][/url]
[br]
Title: Re: NRS v1.2.0e
Post by: no1 on July 03, 2014, 10:18:44 am
sum testnet nxt pls!  :-*

NXT-NFKQ-T26L-WGRN-4HLAZ

thx!!!  ;)
Title: Re: NRS v1.2.0e
Post by: slothbag on July 03, 2014, 10:36:33 am
Given that Aliases are about to become useful, is it possible to include dots in an alias? (currently it only allows numbers and letters).

For example, if I wanted to register the alias nxt.com

Original post: https://nxtforum.org/alias-system/aliases-as-dns/
Title: Re: NRS v1.2.0e
Post by: cc001 on July 03, 2014, 10:39:36 am
Is there any product seller on the testnet that actually delivers ("virtually") the bought product?? I bought 5 different products (testnet product, Kitten Stew, Ecofriendly bag with air, Spam, Stones) and all of them are "Pending". Or did I get something wrong how the system works?
Title: Re: NRS v1.2.0e
Post by: wesley on July 03, 2014, 10:42:49 am
Maybe clients should support some of the labels code

Eg. 
Code: [Select]
[img][/img]
[url][/url]
[br]

If we include images, possible attacker can find your IP (having the image hosted on his site).
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 03, 2014, 11:15:18 am
Monetary system and voting system are next on the list. Although there is no official "list" :)
As features, yes, but before any of those is merged to the develop branch the database persistence branch will be merged and released first, and this is a lot of work (while not having any user visible changes).

I need to check with CfB how Monetary system and TF and Economic Clustering interact with each other, if at all, and in what order they should see the light of day, but this is all after the database.
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 03, 2014, 11:19:14 am
At some point in the future it would be nice to have a 'Transfer my purchased goods to another account' feature, like the 'Transfer asset' feature, if it's possible.
That wouldn't help with security because the original delivery is still in the blockchain and can be decrypted using the private key of the original buyer account.
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 03, 2014, 11:20:53 am
I also noticed that getAccountId API doesnt have "accountId" field anymore, it was changed to "account"
I dont mind putting in an if statement depending on version, but any benefit to changing "accountId" to "account"?
This was done for consistency. Everywhere else in the JSON output the "Id" suffix is omitted, not sure if it is good or not but has been like that since the beginning.
Title: Re: NRS v1.2.0e
Post by: 4747...888 on July 03, 2014, 12:40:38 pm
Is there any product seller on the testnet that actually delivers ("virtually") the bought product?? I bought 5 different products (testnet product, Kitten Stew, Ecofriendly bag with air, Spam, Stones) and all of them are "Pending". Or did I get something wrong how the system works?
I have delivered 4 of 6 purchases, 1 refunded and 1 notdelivered for testing.
Title: Re: NRS v1.2.0e
Post by: sile16 on July 03, 2014, 08:21:58 pm
In my account only 1st of my 3 listed good are being shown.

The 3 transaction IDs for listing:
11832698734889845071
16258001822850582571
11707617898580267056

My accountID  NXT-CMCA-6HB6-PYCF-FYF4D

Even after restarting the client i'm only seeing the first good I list under "My Products for Sale" , However, I do see them listed under: "Newest Products"

Also, (not sure if we are supposed to be testing Aliases as well)
I was able to try and sell my same alias twice in a row for different prices:
txid: 6619862299394914824
txid: 11714173176923994169

There doesn't seem to be a way to list all aliases for sale yet.
Title: Re: NRS v1.2.0e
Post by: cc001 on July 03, 2014, 08:31:57 pm
Is there any product seller on the testnet that actually delivers ("virtually") the bought product?? I bought 5 different products (testnet product, Kitten Stew, Ecofriendly bag with air, Spam, Stones) and all of them are "Pending". Or did I get something wrong how the system works?
I have delivered 4 of 6 purchases, 1 refunded and 1 notdelivered for testing.

just bought 10 passwords from you (I guess it is your product...??)
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 03, 2014, 08:53:38 pm
In my account only 1st of my 3 listed good are being shown.

The 3 transaction IDs for listing:
11832698734889845071
16258001822850582571
11707617898580267056

My accountID  NXT-CMCA-6HB6-PYCF-FYF4D


Must be a client UI bug, calling directly the getDGSGoods api shows all three goods you have:

{
    "goods": [
        {
            "tags": "nxt,money,test",
            "priceNQT": "10000000000",
            "sellerRS": "NXT-CMCA-6HB6-PYCF-FYF4D",
            "description": "10 NXT transferred immediatly",
            "name": "10 NXT For Sale",
            "goods": "11832698734889845071",
            "quantity": 1000,
            "delisted": false,
            "seller": "15387038662948900168"
        },
        {
            "tags": "stew,kittens,yummy",
            "priceNQT": "1000000000",
            "sellerRS": "NXT-CMCA-6HB6-PYCF-FYF4D",
            "description": "Slow roasted gourmet stew",
            "name": "Kitten Stew",
            "goods": "16258001822850582571",
            "quantity": 1,
            "delisted": false,
            "seller": "15387038662948900168"
        },
        {
            "tags": "xss",
            "priceNQT": "300000000",
            "sellerRS": "NXT-CMCA-6HB6-PYCF-FYF4D",
            "description": "hi <script>alert(\"XSS vuln2\")</script>",
            "name": "Sup<script>alert(\"XSS vuln1\")</script>",
            "goods": "11707617898580267056",
            "quantity": 3,
            "delisted": false,
            "seller": "15387038662948900168"
        }
    ]
}


Quote
Also, (not sure if we are supposed to be testing Aliases as well)
I was able to try and sell my same alias twice in a row for different prices:
txid: 6619862299394914824
txid: 11714173176923994169
But did the buyer submit a buy transaction in between? If not, it is just updating the price, but your account NXT-CMCA-6HB6-PYCF-FYF4D still owns the abc1234 alias at the moment.

Quote
There doesn't seem to be a way to list all aliases for sale yet.
Not planned for this release at least.
Title: Re: NRS v1.2.0e
Post by: ChuckOne on July 03, 2014, 10:42:59 pm
So the numeric account format is not going to be supported anymore?
The numeric format is supported in the API indefinitely. Only Wesley's client restricts the users to RS format only. But the exchanges should still switch because the users need to know the new RS format accounts to be able to enter them in the client.
Why the restriction? I want also the numeric account number.

I hope numeric account will always be an option.  It is the only way I know my accounts.

I am not certain why. Could you elaborate?
Title: Re: NRS v1.2.0e
Post by: Jack Needles on July 03, 2014, 11:42:11 pm
I hope numeric account will always be an option.  It is the only way I know my accounts.
I am not certain why. Could you elaborate?

I have recorded numeric account IDs and securely distributed to other parties.  Not to mention API scripts which have been created that rely on numeric account representation.

I'm sure many other users of NXT as a platform have developed a reliance on numeric format.  It would be a mistake to disallow its use entirely, unless you want to break a bunch of services.
Title: Re: NRS v1.2.0e
Post by: sile16 on July 04, 2014, 03:15:58 am
It looks like it's an index issue, from the debug console:

_http://127.0.0.1:6876/nxt?requestType=getDGSGoods&seller=15387038662948900168&firstIndex=0&lastIndex=0

This returns only the first item i'm selling, However if I remove the lastIndex option

_http://127.0.0.1:6876/nxt?requestType=getDGSGoods&seller=15387038662948900168&firstIndex=0
this returns all 3 itmes i'm selling, so, it looks like the GUI is just requesting 1 entry for whatever reason...

so it looks like in ui/js/nrs.dgs.js

we have:

   "seller": NRS.account,
         "completed": true,
         "firstIndex": NRS.pageNumber * NRS.itemsPerPage - NRS.itemsPerPage,
         "lastIndex": NRS.pageNumber * NRS.itemsPerPage

which seems like it may be correct for page 1,2,3... but not for page0    , either that or NRS.pageNumber is not being set properly.

k...

it looks like the issue is on nrs.dgs.js line 240:

      //inStockOnly doesn't work here, need to get all but delisted.
      NRS.sendRequest("getDGSGoods+", {
         "seller": NRS.account,
         "firstIndex": 0,
         "lastIndex": 0


is the root cause of that issue.  Just need to use the same    formula as above instead of hardcoded to 0.





Title: Re: NRS v1.2.0e
Post by: sile16 on July 04, 2014, 03:49:48 am
Another slight bug around the Asset exchange:

When I view bids/Asks around NemStake the price is always based on 1 of the asset.  However, when I look at past transacations, it's actually showing the price per .1 NemSTake.  so, it's kind of confusing and really the past transactions should also be showing price as per 1 unit of the asset.
Title: Re: NRS v1.2.0e
Post by: no1 on July 04, 2014, 09:30:30 am
is there a possibility for a seller to get informed when a new order request is incoming? could the delivery deadline be modified?
Title: Re: NRS v1.2.0e
Post by: sile16 on July 04, 2014, 06:52:32 pm
orders still show pending past the delivery deadline:

Beauty
Order Date:   7/3/2014 13:58:24
Order Status:   Pending
Delivery Deadline:   7/3/2014 16:58:24
Price:   5 NXT
Quantity:   1

Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 04, 2014, 10:25:29 pm
Something is wrong with the delivery deadline calculation. For this purchase, deliveryDeadlineTimestamp is 1404424704, which is way too far in the future. I have no idea how Wesley is calculating it, for 3 hours deadline should be purchase timestamp + 3 * 3600, which for this purchase makes 19130304:

Code: [Select]
      {
            "priceNQT": "500000000",
            "buyerRS": "NXT-CMCA-6HB6-PYCF-FYF4D",
            "sellerRS": "NXT-REN2-VEWP-HR79-32E56",
            "goods": "17662085307137378262",
            "purchase": "2310115758276953844",
            "deliveryDeadlineTimestamp": 1404424704,
            "noteNonce": "f5384ac27b9d9db21ad8133b920f8703d7b91f17d6bf1bfb6542f6b58d5933ba",
            "seller": "1300837546428445312",
            "timestamp": 19119504,
            "pending": true,
            "name": "Beauty",
            "buyer": "15387038662948900168",
            "quantity": 1,
            "note": "35429d946eb7352c137a1cc8909c63ac0615da35f42d09f1cbb25c93c50a810be1fe317fc17a3d2c4e2cc23f5e33716a3473522722ac1422a9ba4a5e92a40832ade90acda42d95cdcb4b3fd43f7c0bd5783503616961330962002a0b5231603cfcc91fa603f72c0311ab0314ea2c622b115de428c79a131080bba85414c32ce47911be216f2bde0afc3d995ae02cf3af5b67a816e55bf209ed0e3eacd2d37b0e6fc19c3e4fc31c5c6c91168d87b06cef"
        }
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 04, 2014, 10:28:12 pm
is there a possibility for a seller to get informed when a new order request is incoming? could the delivery deadline be modified?
The deadline cannot be modified. For notifications, possibly, you mean with a pop-up like when you receive an asset?
Title: Re: NRS v1.2.0e
Post by: MyZhre on July 05, 2014, 12:35:43 am
Something is wrong with the delivery deadline calculation. For this purchase, deliveryDeadlineTimestamp is 1404424704, which is way too far in the future. I have no idea how Wesley is calculating it, for 3 hours deadline should be purchase timestamp + 3 * 3600, which for this purchase makes 19130304:

The value 1404424704 looks like a unix timestamp : Thu, 03 Jul 2014 21:58:24 GMT
Title: Re: NRS v1.2.0e
Post by: PoofKnuckle on July 06, 2014, 09:49:01 pm
Maybe this will help. It's a couple of pages with JavaScripts to convert NXT timestamps to a human-readable form. They have some explanatory text on them.

http://cl.ly/3v2r3r1s1q31

Title: Re: NRS v1.2.0e
Post by: PoofKnuckle on July 07, 2014, 12:23:57 am
It would be helpful to have an explanation of the new APIs, like here:

http://wiki.nxtcrypto.org/wiki/Nxt_API

Does this exist yet somewhere? I can tease out most of how the APIs work using this:

http://localhost:6876/test

and watching the results in my browser's Web Inspector.

But there are some fields that are not obvious to me, such as deliveryDeadlineTimestamp and encryptedNoteNonce in dgsPurchase. I can't figure them out because I can't guess what to put in.

Title: Re: NRS v1.2.0e
Post by: Isildur23 on July 08, 2014, 10:01:08 am
I have purchased several goods.
I decrypt one, give it feedback and then i opened another one. Before i decrypt it though, under "Data" i see the previous good. Here are the screenshots:
(http://prikachi.com/images/841/7454841p.jpg)

(http://prikachi.com/images/852/7454852k.jpg)

(http://prikachi.com/images/854/7454854Z.jpg)
Title: Re: NRS v1.2.0e
Post by: Isildur23 on July 08, 2014, 10:14:14 am
Not sure if i have to write this here (so tell me if i have to move it):
1.
When i scroll down in the marketplace and i see a good which has "Show more..." under it, i click it and then i am forwarded to the top of the page, so that i have to scroll down again and find that good (the description has unfolded and there is "show less" under it as it should be, the only problem is that i had to scroll down again).

2.
I can't see the quantity of the good. I know i can click on seller and then go to marketplace and see his asset and its quantity, but i think for users would much more conveniet if they could see the quantity right next to the good.

3.
When i click on Seller on the right side of the item/good it just doesn't open, nothing happens. I am running 2 different accounts at the same time and forging with both, i don't know if this fucks it up. But the other account works fine, i click on "Seller" and it opens.
Title: Re: NRS v1.2.0e
Post by: TeamWealth on July 08, 2014, 10:39:35 am
Potential? Bug i found. If i try and buy the Watch Dogs digital deluxe edition uplay key listing and paste this into the note section it gives an error about the listing not being valid

äÆûßÚÒÉÓÕúÀ³ÞÇÚé«ÀßÝʪý¡³á¥Æ´¡£Í²ÁÑãÑâÅé¯ã«Þ¤ìµñóÛÏöÜÕúÖ¹ßÕì³´®õÜÃùóÙ×Àêþù¯¸®é²«ß»§Ü®ùÑÄ߶¼¼¨ÛÜí»ý婥Ŀ٧¾ðöЪ¸êëûѽåøâ¹ëðñÇæàÊøÎíèŵ³ÜÛïÒÎóÓ¥§äó½¬Â»°¼ãåÂðÎÈÕ¼¤ýÚÖóÚܸʡØöÜßöé·ôÿøÃÇÝÁÞ¬ØÁâæîÁ×®«ÐÈÜغ¸åÓ·ìÚÊÏÇ¿÷ªÝÒäµîº¸Ö»ôâÄȼíÐú¶¥¸Þ䬬ÝØäÍÂîÞ¯¯â»ùü¨òó£äùáý«Ð½øäÒÅïòìÒ÷¡ë·ù㤽¡ÃÝÏû¤±óÊî¾Ëúèà´ÍÐÜÙªÅʧÐÔþèÂéÆñÎãùÅëÈó¿×¬÷ÒÉÙª®î®¼Èôø«ÄÎ×µìÝÜ·ó°Ëê»Ô©Í¤ä¹ìᢸܪ»Ôä˲ױŧ¤§øÏÃÂæÇ×¼¥èãïµÀÛ©ê½Ñª°ÉöÁÂÛæ°»¥¶æÖÅûé´²øϬíÒ§¡Õ´çöú×ã×þä°ûØÐÈdzäé¨×Ìà¹ä²àüÆ»ñ«ßËðÛ§«í먳ɰ½ïû¨ÍŹð¿ëûáÁæ¢ÁÑÏ»´§¼¼þ¬îºí¹ßÆ»ì®ËÇøìÄÜÀסͤ¸¦ÏиÁã¸ÓÚÓó¥ÁôÄÓ¿ïðþîü;ùñÚ×ÀþùæàªÈ»ÝÝÜÉͤõ¢ãÓñæÎÅóéÅîÃÏÿîèÁÚ½©øçʨ«¾»ý»¬÷ô˶öøØÇ®ÔÄ×ç»ë÷Ê㬿°ñÚÆ·ùñËü¼¯þϳ±ùÛÍØ»µ£¹¸´µ¿Ëíظº§÷÷ÿΰ¸¢ÆþÈëΩ¡É¢¥öôÇØÅðüÝòÏåÍòÝàÔ¼ª£Æ³¾ÖèÇå÷î©ú÷ÝÏóÅÍ̾Á¥êÆõ®ë¯·ùÛí¸§½ãí°Ú´ÃáÐøñÿÅùùµ±ó¹ÁêÁ¬ÃóªÚﻶñÁãðÓí¢é¥¹»íâÓÉìã²ÆìÔ´å¸èزßõ»ø«ú×à½èÃü渶ɰúìçóûÈûï禮ձôÃËæûÊɹҨèºç¸ÊÝÉÔÒûüµêÝÒçÛ§ÑÈ×ÁøÌ¥Óýýñ¬³Ü³ïøÚ¡°£µ«þÂÚÜñ±ýçó˶µáÁ¿¾¡½»¿ÛðïúÒâ¶ÆÅƪËð°¢Úããß঻é³àÐé¤úéÓȹ¸¤ÇüðÊ»ÿþíõäÜ鸦ñÅÀùÀ¦òô©¶ÑÍÉÄæܼîÆÀ¹©ë÷¢ßãÉøÀÏß»ÖÒ±¶èÎôþö¦Òáõíè°ç»ÝÐÞ¾þû®ÆÕÃíúà¡÷êÌÊòíûß˦ú×ÎŪ¤èæ¯úô¸ÌÇö

The error being


Quote
Invalid digital goods purchase: {"priceNQT":3000000000,"goods":"9228989798507777613","quantity":1,"deliveryDeadlineTimestamp":1404987600,"noteNonce":"1a2f40d57f7f4bf08372843d4113c6cce17c5c4a658f8ec75b828e7484231779","note":"26fd22df1bcce259e139a5fc3e0522516133e4a37f64655a698c33e7845e35e2cf1aee4ee95250c996245d2d5acbf0f62c1122b6eca2f9a88b18c07532a9f051b70ecaa79206ea96742b481d6ffd130cfdb48c2a549336e216c19afd2ea70afad6b617f80c5aa7f2c8bc427acde95fb11e6d7a82f79f05c6ec46734a7637297ad8da8c5715b5553afea0980251ee28ecaedfb8b5638c9a68ad8e4b48f7baa3067fc439841070e55c11dea201c7cba370f2416e4279ce8f9d3cbcf8a1d530aba0282f59960978d488d65f2fdc98590ecc7bccc2c5fc3239c9d4d4231a40259621b4357a4999ce612f0b4ea49ce92a25b59f07b5946b59214175fac79ca9007918c0bc8c1bede89c089d9389faae16d9a53d98e28a7929403cbf3a4b484cfb09ff7e4fb3f7246e0619c9a65d879fb055ad0076206c19b66ccba87f2c9897d7c33461e8a40d2fb85427a1f2d8c5080a563522ef576559df2a90feceb3eb3afc1efff9a876d3062202faea291f0c0d67cf707c7d3684bf72ec61c9b8813c7efdc9bd9b98e81f64fc75882e07fdc529d4324ffc80618a07e3d04c1af641e7718aa80c82ba5bbd539c059864229d5a47f94f5f526e0f515320776c1ba6d312b0382cb274f5e38aaa4d081c04bb1b6697df6b37be84113d0a78cef94f4d0d8036348c087921434ee4047f7e463da30d142720a11e4056730b41481df1156dac117c90c8e073f74f67682b43e2904e93921f0002d8ffe9a7d65485dce7783380a98086cd2886bbaaef45b8e0f0c832502ae6774e5d54206493a577bab51c6b51d5ed19c6cc33bcf06b16ace9e093772c6c8874c27f863774550f189ed09ea7b822d7f589d90b2c305bb20378fd87bda59eeaa69969b57ea6344f9d58513fb183600536a18e65d076a9dde5503fe639ab116557ad117b5da628a4c22eccf2802097deaaa1134ff8478aec07ec11bfeec5b657e8408866a6924eb7837f434eb88eb5c1f5fa74c34b9672a87ea429038d649493124e9f3dc48cd37492403341c74a4ad0ef8dfa380cf0d2a8693c0ae1c16f7b8c90eba18d3bc1fbf73de24355520f197b60668c90a3b978cff42b10b1cd8c83d64ffd3a43757edb3754e45a60fa85919da1e8788b54df4f5c86bab327676c1be187520fa6786190cced9c876bf73f3082238d299c0e7b19bac71e2b4bcbe60db966b5f40c4afa306a7eb8fece89222d8deb800dedf3288d0b1109a55eea5389a715ead7ee4fc54beff9b5ccd1144f9e57346a49803778001ab292a064ade38c8c748cd43845f429980f1d45ad41792270a11c6c58742c160814d8c8ed98b57314a07dc676d786bd09c2b482e0628610dba36a63fe5699e86541a9ef7df92583d06538af7c4a437e66b522af6741643bb3fb54c21fe3868f4fae46199d457de5f32ea04167cefe3e3a7cf39e2c80de73c904d7fb570ced667935684d32b194f90ed9893a2de074b311450730df6dd3850d0d5d81ee39b6a0a2e7906b9cd33ef393aad27112f5a7ac1b9c5401a5e749f0c3cfe2367a642972f7e95a70f520016d10d3e270cb07aadd0159537bd673807063846c7aed86630e5c089d7bcc6d09f403bf49c7c61a0ed9684df9206c10cb3b16011f928ade97dad04bbdc47dce5149b72bcefe4397b606e468cf1a456b281706d17c5f3c734fbcd6fc65b6301312b32de401d980d116aa0c7809c1c68d5cb23368b3"

It may be that there just is no error handling for the encrypted text exceeding the maximum length for it to be transmitted to the network? The note is 999 long.

Edit, it was invalid with a 980 long randomly generated pure ANSI but fine with 980 standard letters.

Note after this i switched to the jokes list and some of isildur23 as they were cheaper.

Edit two, Two times with two different 800 character ANSI characters it worked on two different DGS purchases.

Edit three, at 803 ANSI characters it occasionally works depending on which one it is and sometimes it doesn't. Below are two blocks of ANSI crap one which works one which doesn't.

Works: In keepass it shows as 5196 bits so i dont think that has anything to do with it.

ä¤ÐÊÖÿ¥¯æ£õöÒêÞç˧ÏýýÚã×ý°¥üüâ¡¢ÒáòÈØТÎ×Ô»¿Þºë÷¿íµ÷ñÙ¨üòËÿÚÊÀðîù¬úðµ¶ú¬Ö±º¹¢£¡è¯å×®¤ç®©Ú³û²ù°ÅÃË¿ä½ñêÆé¦ÚÞ£øû¨ïµØÇÈܵ«ç±ÆÍ¥ÐìùêÞÚÅò©ÿ¢¾ÈÏߢÏòô©ÖÒ¤º®¥ü²õý¥ÄÊÜ¢ëá±èÓò²ã¢¤ØûåµÑ±á¶ºá¡×ÄÿÕ¾Ûµú«Äþ¡ôÔô§±®°ØïÕ£ÝÃËÊÞºÇÈÀ´øÅ¥Ô̹½´±¹ÛÙÔÀ¢õ£Ý½ªå¯ã«ÔåªÏ맡ðìÃÕ³ÆäñïÑë½ÖÌûÈâ¥ÉáÎ㣰ӷøÏÎý³àëãöØÿäâ«âåúƼäÏÁ¦ÁéÜùäùéÃèÓÌýý룤¥èÖضÇƵ´ÈèÁÌÎÉéý¯µÄƫ窾°ôãÏÓþ¢¼ÊÞßÂùÓŶöÊ·¹±üź½ÀÔ¬¥ÞÁà×æÄë¾Í¡µ¥äæÌ«ÖÊÎôûùÎÒËä뢶âµþà¬Ù±¢îâáƦå¬ÿ»ÜÜøãéÚ¸ÈÅ°¸ÀéÔìÞÜí³ÂûÈøÝÓðµ©ãèáÀñùì¶ïö¤Ù§ùð´ÿ»Ù¢ÉïéÙáÊ°ðåìë´³ö¾Ý÷ñØÐØ»ç÷¨¼Ã²¾ýßǸÔø¯è½ìܱà¸ùÓ×þÓ×·¾¦¸Ù뽵ƽ¿è£º×«åعÓòÚ¢ÓÔåçÍô²¹ÙôÛûè¦à±þµ¼Ðôµþ¶ò¤âõ±Ô÷·½¹³ÍªÖÍÁúîõ¿¬®®ë³Þ´¨Ûü÷Éçëÿñ컶¦ãÏʱ¹¼ÉÂÀôÖÜ®¨³¹¼»÷¿¼¦»Úôä·óê½ÙøÄÖ÷êðþ·¹àò·Â®ÓÀö×òúü×æì¸ìáò²¼åÆâÒÙíôÕÀîìãμ¦ÇÝ©ÿ¾Å¬¤åÈûïËÒé³½ÄÝ·Úùýᢵë¾×¥À»íýöµÚƺ¯ãðÔ·ÞùÒ§ÓùݺÐÐãçæ£Ñþí¿çݹª¼ÞĦËøÓÞ¢ËÂ怜£ø¾öâÒ¸ð¯þÿ©§Í׺°ûáÎͲóűÇè«ø¯á½ÌÞ³êíæ¬Æ¤³¥Û°¹ªÇ¸¿

And one that doesn't work. In keepass it shows as 5165 bits.

÷õÎúú³óÆÓ¼²ÀóÙ¯þþ²ºÞ÷£ÑñÙɲÄðÅÇçñºíî×Õ¹¥·ü×Ò³ÿ©Ø͸äáí÷ãÉϳæê¢î¸¤¸ÄÕÜÅÂÑÉüæ³÷ýýÐú¶¾ÙÆ¢áÞÁ¤ÏÀ𦤴¨Þ½¡¨Ãßì̾¤ÉÌ¿ö¾£âÏó¹ößç¸÷íÅ¿èè¤ðûòؼ쿣·ÇѪ³ÀéÍñÒÔøöÝÚ«ÆÉã¼Äææºîéí¸íÐðÒù¹ñ¥ÀÉÍÑÖéýæÈ÷°·ýÖ¬ÿ²µóÂß¼þ»¡ÎÈ´èäàÚÁöÖ®»Åº·ìïʪ縹ºÌú¯§¸Òí¸ÝÈßÌô°µÚÓÄÜƱßìÉ®¤ÄÕ³ÓÖ¶¬Ì¢·¦ö¼ê٩ɼááèçñòϸöªá®íËåúãýû˼áÎãç©éæÓòóÏ¡óßîÿ÷Ûºáóôðâþ¦¼½²òıÆì̶֨äÆ¢ªÈËȺȥټ¦¨ÒàþòÈùά©©÷¨ô¡±ËûèÛ×ýÚü«ÇÔѾ³ßéÏø𵩹ԴǼù÷àÃïïýÀþÏÅÙʸ¢èº¥ªö¾©àß¾Ññ¿Íö»Íö°îÝÛ×ú¬È®ÀìµéïïÇ×û£¢ÂÉøÐéà¡¥÷ý½ô¨íú£Ú×¹üɨñ½¿«º¯¤Õ̯îô½¡Ý§Üõ²èï®ûÞ²ÛÁ¿ÅÑÌÇÀçÅñîËѧÊÆé®Ö¼ÒÎÊ´·û¢Å÷먪ÎÂ¥¢þçëÛó߯ÑîÂÇÒìüº³È¢ÎÚ¶ûÊÄË×ݬ˵ÞðÖäÞ÷̲ÑçÅíÿ©¥¦çðèÓɽ¾¼ôçÙÈ¿åÃãóþ¬÷®ÎãÆÚ¦ßÌÇîâöñ£ÃÎçàËùҷ樫ÍØûÄãÜǶ¥÷¢ÖùÏðÞÓð¦À濹üç¢ê·×Ôèà¿ÅÜÿÛ¨¨Éö®ãع¦ªäó½í÷·ÔìÛÑçÞ³¿çýÁ£æñ¾Ü½ðÕ¹ýø۵ʦӢÅòï¸ôàÑý»¹ôëµâÓ©õåƶ¡£ô×ûÁú°ö¶Í¨ÁÙýÉܨõí§¼Ú¡¤òöÆЫÑÊéî±ÖÈÿÆà³÷âµÿÌÝÃÿ¼«£¾¿Ó¿á´âßàûú·´¦îÇÚ²¼×»ßÒ¿óæúÞüÿ¹®¯Ñ¨ÉéáùÂû®¡


I am not sure what else to test to see what else may come up with usable information, let me know if you can think of anything i could help with :)

Title: Re: NRS v1.2.0e
Post by: Isildur23 on July 08, 2014, 10:45:33 am
orders still show pending past the delivery deadline:

Beauty
Order Date:   7/3/2014 13:58:24
Order Status:   Pending
Delivery Deadline:   7/3/2014 16:58:24
Price:   5 NXT
Quantity:   1
Same here
Title: Re: NRS v1.2.0e
Post by: TeamWealth on July 08, 2014, 10:46:40 am
orders still show pending past the delivery deadline:

Beauty
Order Date:   7/3/2014 13:58:24
Order Status:   Pending
Delivery Deadline:   7/3/2014 16:58:24
Price:   5 NXT
Quantity:   1
Same here

Same, not getting refunded the NXT either so its not just a graphical glitch with the unfinished ui.
Title: Re: NRS v1.2.0e
Post by: valarmg on July 08, 2014, 11:40:58 am
This isn't specifically related to 1.2.0e (though it happens with this version too), but when I have NRS running for a few hours it'll start to eat up my resources and slow down my computer and I have to restart NRS to get things back to normal again. I'm running Windows Vista 32bit.
Title: Re: NRS v1.2.0e
Post by: Neomadra on July 08, 2014, 02:15:06 pm
I'd like to test, too. Can someone send me some test-nxt?
NXT-PX3B-CWKZ-KM6S-C4DFG
Title: Re: NRS v1.2.0e
Post by: kodtycoon on July 08, 2014, 03:14:47 pm
This isn't specifically related to 1.2.0e (though it happens with this version too), but when I have NRS running for a few hours it'll start to eat up my resources and slow down my computer and I have to restart NRS to get things back to normal again. I'm running Windows Vista 32bit.

i run the same system and that doesnt happen to me.
Title: Re: NRS v1.2.0e
Post by: v39453 on July 08, 2014, 03:25:44 pm
Can I have some testNxt? Thanks.

NXT-JYU4-XRNB-A7SC-29NQ6

Title: Re: NRS v1.2.0e
Post by: valarmg on July 08, 2014, 04:26:15 pm
This isn't specifically related to 1.2.0e (though it happens with this version too), but when I have NRS running for a few hours it'll start to eat up my resources and slow down my computer and I have to restart NRS to get things back to normal again. I'm running Windows Vista 32bit.

i run the same system and that doesnt happen to me.

Don't know. It just happened to me again a moment ago. CPU usage spiked to 100%, and chrome became super slow to open a new tab. I shut NRS down and it went back to 30%-ish. Restarted NRS, and CPU is still 30%, but I'm sure the CPU-jump will happen again at some stage. I am doing some GUI design for NxtServices (but I haven't been running NxtServices core today), don't know if I'm hitting some weird sequence of buttons that is causing it.
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 08, 2014, 10:27:55 pm
But there are some fields that are not obvious to me, such as deliveryDeadlineTimestamp and encryptedNoteNonce in dgsPurchase. I can't figure them out because I can't guess what to put in.

deliveryDeadlineTimestamp, specified in seconds since genesis (current 1.2.0e version has a few bugs here and doesn't work) is the deadline by which the seller should deliver the purchase. After that, the purchase is no longer pending and cannot be fulfilled, and the buyer unconfirmed balance is updated to release the funds reserved for the potential purchase (minus the transaction fee which can't be refunded).

The two "encryptedNote" and "encryptedNoteNonce" parameters are to support client-side encryption of the optional note attached to the purchase and some other DGS transactions. If doing the encryption in the client, to avoid any sending of password to the server, you have to supply those two. Check with Wesley for the javascript code that does client side encryption. Alternatively, if you trust the server and have a secure connection to it (or is localhost), you can specify "note" parameter instead, and encryption will be done server side.

The encrypted messages are done with a random nonce so that a different key is used for every message exchange even between the same two accounts. Thus the need for a nonce parameter when you do it client side.
Title: Re: NRS v1.2.0e
Post by: Jean-Luc on July 08, 2014, 10:57:00 pm
It may be that there just is no error handling for the encrypted text exceeding the maximum length for it to be transmitted to the network? The note is 999 long.

Edit, it was invalid with a 980 long randomly generated pure ANSI but fine with 980 standard letters.

Note after this i switched to the jokes list and some of isildur23 as they were cheaper.

Edit two, Two times with two different 800 character ANSI characters it worked on two different DGS purchases.

Edit three, at 803 ANSI characters it occasionally works depending on which one it is and sometimes it doesn't. Below are two blocks of ANSI crap one which works one which doesn't.

The length limit for note is 1000 bytes, but this is after compression and encryption of the plain text. If it is random, likely it won't compress much, and near the limit small changes may make it go over or under when compressed and encrypted.

Notes are supposed to be UTF-8 strings, not binary data. For Goods deliveries, goods can be either text or binary, but the browser client currently doesn't let you submit binary goods (using directly the API should).
Title: Re: NRS v1.2.0e
Post by: TeamWealth on July 08, 2014, 11:03:16 pm
The length limit for note is 1000 bytes, but this is after compression and encryption of the plain text. If it is random, likely it won't compress much, and near the limit small changes may make it go over or under when compressed and encrypted.

Notes are supposed to be UTF-8 strings, not binary data. For Goods deliveries, goods can be either text or binary, but the browser client currently doesn't let you submit binary goods (using directly the API should).

Yeah i assumed that, Probably just needs a tiny bit of code for error handling of that in the client saying that the message is to long so it doesn't say that the market listing is invalid. Either way its an extremely minor issue.
Title: Re: NRS v1.2.0e
Post by: PoofKnuckle on July 09, 2014, 12:51:53 am
Alternatively, if you trust the server and have a secure connection to it (or is localhost), you can specify "note" parameter instead, and encryption will be done server side.


Excellent, thank you!

Title: Re: NRS v1.2.0e
Post by: Sebastien256 on July 09, 2014, 05:56:17 pm
Hey, I just want to say congratz on the Digital goods store. I just test it on the testnet and I think it work nice!

Great Jobs, Really!

Now, I just to need to find something I can sell on DGS... ::)
Title: Re: NRS v1.2.0e
Post by: cc001 on July 10, 2014, 08:42:28 pm
is the issue known that if you want to change a price of a product a minimum price of 1 is needed (PriceNXT: Minimum value is 1.)?

edit: as well as the "Discount". Fractional NXT must be possible.
Title: Re: NRS v1.2.0e
Post by: cc001 on July 11, 2014, 09:12:47 am
Wesleyh: could you please make it more obvious when I (as a product seller) have pending orders (delivering products). Something like a visible counter, something like (2), when there are 2 pending orders.
Title: Re: NRS v1.2.0e
Post by: msin on July 22, 2014, 05:17:17 pm
Small bug:

I clicked on "Purchased Goods" then a specific good that I bought (that was delivered), after decrypting the data with password, I closed out the box and I clicked on another purchased/delivered good that needs data decrypting, but it displays the data from the previous item, after I decrypt the data it then shows the updated data.  Hope that makes sense.

Also, is "feedback" something only the seller can view once I leave that?
Title: Re: NRS v1.2.0e
Post by: Berzerk on July 30, 2014, 08:31:34 am
Can someone ELI5 to me "database persistence" and what differences it makes? :)
Title: Re: NRS v1.2.0e
Post by: LocoMB on July 30, 2014, 04:15:43 pm

Hi Guys!

Is it just me or is the 1.2.0e testNet some flaky? I seem to be in forks all the time, did I miss anything?

Best, l8orre
Title: Re: NRS v1.2.0e
Post by: Pilot on July 31, 2014, 05:03:04 am
ELI5

What is that? I see it quite a bit.
Title: Re: NRS v1.2.0e
Post by: LiQio on July 31, 2014, 05:04:53 am
ELI5

What is that? I see it quite a bit.

"Explain Like I'm 5"
Title: Re: NRS v1.2.0e
Post by: Tosch110 on August 01, 2014, 02:53:57 am
The two "encryptedNote" and "encryptedNoteNonce" parameters are to support client-side encryption of the optional note attached to the purchase and some other DGS transactions. If doing the encryption in the client, to avoid any sending of password to the server, you have to supply those two. Check with Wesley for the javascript code that does client side encryption. Alternatively, if you trust the server and have a secure connection to it (or is localhost), you can specify "note" parameter instead, and encryption will be done server side.

The encrypted messages are done with a random nonce so that a different key is used for every message exchange even between the same two accounts. Thus the need for a nonce parameter when you do it client side.

Can you give some more insights? I am using php. I have tried to decrypt the Note via the API but did not succeed. (The same for goodsData, feedback?)

Do I have to use 'readEncryptedNote'?

Another thing, is there a way to find amount of confirmations for any DGS purchase? I just see timestamps in seconds for DGS purchases. Would it be recommended to wait 10 Blocks minimum before delivering a purchase?   
Title: Re: NRS v1.2.0e
Post by: vladimirceman91 on August 01, 2014, 07:05:14 pm
So what's the ETA to new release?
Title: Re: NRS v1.2.0e
Post by: VanBreuk on August 04, 2014, 01:50:58 am
We were wondering if the UI (?) bug in 'removing assets from bookmarks' has already been addressed.

https://nxtforum.org/index.php?topic=4211.0

This is when trying to delete an asset you have sent/sold out completely, and the client still reports "you own it" with asset balance 0.
Title: Re: NRS v1.2.0e
Post by: slothbag on August 04, 2014, 02:54:24 am
Is there still plans for another test release or will the next one be a full release for main net?
elective-stereophonic
elective-stereophonic
assembly
assembly