Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 1452. (Read 2761645 times)

legendary
Activity: 1176
Merit: 1134

Guys, u were talking about splitting the bounty to 4 parts. Did u come to a decision? If u r agree to split the bounty then I won't spend time on speedtests.

Well I wouldn't mind. We all spend a lot of time coding. I guess hoax and gimre don't mind too, but I haven't heard Jaguar's opinion yet.

Ok, let's wait for Jaguar.

How much work is it to benchmark all 4 on the same platform? I would like to know the TPS and I think it makes sense for there to be published performance and also test results. Since it is JS, doesn't that mean it is browser specific? Do all four run on all popular browsers?

James
legendary
Activity: 1470
Merit: 1004

Guys, u were talking about splitting the bounty to 4 parts. Did u come to a decision? If u r agree to split the bounty then I won't spend time on speedtests.

Well I wouldn't mind. We all spend a lot of time coding. I guess hoax and gimre don't mind too, but I haven't heard Jaguar's opinion yet.

Ok, let's wait for Jaguar.

He's busy with NEM.  Question for CFB; Is a Reputation System being developed by JLC or You? (or plans to develop)  I was going to offer a bounty for a working version, implemented using public AM.  
full member
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.


Erm what's the processing time for every thousand transactions... sounds a bit like avatar mining Cheesy

It's fast particularly if you cache and use timestamp.

Or, a service provider could certainly maintain an http accessible cache. If you're not into the decentralized thang.
legendary
Activity: 1176
Merit: 1134
Does anybody know what time the strange fractional orders on dgex got cleared last night? For a few hours bter was trading 50% above dgex. That is clearly unsustainable and my guess is that the bter market got arbitraged down to the dgex price. Since the dgex price seemed to be stuck, this means the downward move from .00016 was not due to big seller, but arbitrage, or perceived arbitrage. The NXT/CNY value peaked at .85 and dropped to match the dgex price.

It seems the dgex price is unstuck now and this bounce at .00016 is the second time, regardless of the reason. It is not uncommon for a price to bounce three times before breaking out. I think it is good that it has come back down a bit as the rise was too extreme. Gather some support at .0001 and gradually get back to .00016, bounce back a bit and then finally breakthrough. That would be a sustainable pattern that would then turn .00016 from a price ceiling (resistance) to price floor (support).

Of course, this is crypto, so anything can happen, but I think there is a significant amount of fast money parked in NXT right now, so it could follow more standard technical patterns

James
legendary
Activity: 2142
Merit: 1010
Newbie

Guys, u were talking about splitting the bounty to 4 parts. Did u come to a decision? If u r agree to split the bounty then I won't spend time on speedtests.

Well I wouldn't mind. We all spend a lot of time coding. I guess hoax and gimre don't mind too, but I haven't heard Jaguar's opinion yet.

Ok, let's wait for Jaguar.
legendary
Activity: 2142
Merit: 1010
Newbie
Thanks, that did it! I think it slipped in when transferring the api from the wiki.

I also seem to have a problem with the deadline - docu says it should be in minutes. I get this reply for every request that has a deadline, sendMoney as well as placeOrder, etc ...

Do you see anything obviously wrong in the query below? Is maybe the 'REFTRANSACTION' to be dropped out of all queries? Thanks!

http://holms.cloudapp.net:6874/nxt?fee=1&secretPhrase=xxxxxxxxxxxxxx&requestType=sendMoney&amount=43&deadline=30&referencedTransaction=REFTRANSACTION&recipient=9998590259914237067

Get rid of referencedTransaction.
sr. member
Activity: 952
Merit: 253

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.


Erm what's the processing time for every thousand transactions... sounds a bit like avatar mining Cheesy
full member
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".


Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of . More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.



Yes, I know this is how its done currently - but that's horribly inefficient.

You can limit the transactions with a timestamp - first to the date that NxtAvatars are introduced and then to last time an avatar was fetched. Transactions are now ordered so it should go quick.

legendary
Activity: 2142
Merit: 1010
Newbie
Yes, this would be the solution - if that alias of account number was locked and only the account itself can own it, then we can do this. If it is squattable, then it isn't possible to do.

CFB, what are your thoughts?

Squatting is allowed. Let's find another way.
sr. member
Activity: 308
Merit: 250

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".


Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of . More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.



Yes, I know this is how its done currently - but that's horribly inefficient.
full member
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".


Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of . More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.

hero member
Activity: 687
Merit: 500

Guys, u were talking about splitting the bounty to 4 parts. Did u come to a decision? If u r agree to split the bounty then I won't spend time on speedtests.

Well I wouldn't mind. We all spend a lot of time coding. I guess hoax and gimre don't mind too, but I haven't heard Jaguar's opinion yet.
sr. member
Activity: 952
Merit: 253

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".


Prefer to store a link to the avatar which any client can pick up.
Expanding on this...
How about this - all accounts automatically own the alias
This alias is locked to the account.
You use this alias to store in URI format a hierarchy of parameters for the person who owns the account - this can be set and managed though the clients - one of these is the avatar.



Yes, this would be the solution - if that alias of account number was locked and only the account itself can own it, then we can do this. If it is squattable, then it isn't possible to do.

CFB, what are your thoughts?

Well if is currently squattable you could always release a 'special' that is not available in the current code like @ or pick a prefix string that no-one knows when you do the code update guys Cheesy
sr. member
Activity: 308
Merit: 250

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".


Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of . More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..
sr. member
Activity: 897
Merit: 284
Any consensus been reached on how to get an avatar that matches to an account? I know there was some talk about this some time ago.
What do you mean?
do u mean avatar on bitcointalk?

No, an avatar mapped somehow to a Nxt account ID. (to be used in messaging apps)

Couldn't we convert a small image to a base64 string and insert it as an alias transaction? The downside here is blockchain bloat.

That's not necessary, an URL is good enough.

However, the issue is how do we know which alias refers to the specific account avatar? If we use a special format, that can be squatted by others.

I guess one option would be for someone to create a site that will host all avatars. User sends AM to site account with avatar URL in it, and then it's possible to do site.com/3434343434.png to get that account's avatar - or a default one if not specified. But this is centralized.

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".



This is also a good possibility! We would have to go through all aliases a user owns though, but this should be 1 time only. Still prefer the other solution with locked account alias id's.

With locked alias account id's, we open a whole new ability to have an actual profile to go along with an account. could be very useful down the road.
legendary
Activity: 1181
Merit: 1018

I seem to be having issues with a few queries - eg:

http://holms.cloudapp.net:6874/nxt?&requestType=getAccountTransactionIds×tamp=0&accountId=7126304194855053556

errorCode - 3
errorDescription - "account" not specified



Use "account" instead of "accountId".


Thanks, that did it! I think it slipped in when transferring the api from the wiki.

I also seem to have a problem with the deadline - docu says it should be in minutes. I get this reply for every request that has a deadline, sendMoney as well as placeOrder, etc ...

Do you see anything obviously wrong in the query below? Is maybe the 'REFTRANSACTION' to be dropped out of all queries? Thanks!

http://holms.cloudapp.net:6874/nxt?fee=1&secretPhrase=xxxxxxxxxxxxxx&requestType=sendMoney&amount=43&deadline=30&referencedTransaction=REFTRANSACTION&recipient=9998590259914237067
full member
Activity: 168
Merit: 100
IDEX - LIVE Real-time DEX

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".


Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of . More on data urls
5. Rejoice.

* Avatars can be updated by sending a new AM to the avatar account.

nxt: 4915862015826193000
sr. member
Activity: 308
Merit: 250
Any consensus been reached on how to get an avatar that matches to an account? I know there was some talk about this some time ago.
What do you mean?
do u mean avatar on bitcointalk?

No, an avatar mapped somehow to a Nxt account ID. (to be used in messaging apps)

Couldn't we convert a small image to a base64 string and insert it as an alias transaction? The downside here is blockchain bloat.

That's not necessary, an URL is good enough.

However, the issue is how do we know which alias refers to the specific account avatar? If we use a special format, that can be squatted by others.

I guess one option would be for someone to create a site that will host all avatars. User sends AM to site account with avatar URL in it, and then it's possible to do site.com/3434343434.png to get that account's avatar - or a default one if not specified. But this is centralized.

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".



This is also a good possibility! We would have to go through all aliases a user owns though, but this should be 1 time only. Still prefer the other solution with locked account alias id's.
sr. member
Activity: 897
Merit: 284

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".


Prefer to store a link to the avatar which any client can pick up.
Expanding on this...
How about this - all accounts automatically own the alias
This alias is locked to the account.
You use this alias to store in URI format a hierarchy of parameters for the person who owns the account - this can be set and managed though the clients - one of these is the avatar.



I like it Smiley
hero member
Activity: 840
Merit: 1002
Simcoin Developer
Yes, gravatar for account Ids.

I mean, why don't we just use it?

We can create a mail server and give users emails like "[email protected]" then clients can pull avatars from gravatar.

Don't see a point in creating a mail server when we have AM.

Yeah, I guess it's better to store them on blockchain. Just need to figure out how to find them among all the messages in user account.

We need some sort of file system on top of AM, which will use AM as clusters and provide files.
Jump to: