NXT :: descendant of Bitcoin - Updated Information

[smartwart]

And lets combine one user his split-capital due to weighted VPS-Nodes to forge...
-Hammer-Feature-

We need to introduce measure that prevent everybody to forge @ one VPS because as the result will have this only one VPS. There will be no reason to own nxt node

not sure if I understand your point in right way.

I want to describe the scenario more detailed:

+Many user have more than one VPS-Node - each.
+This is good because Network becomes more robust.
+This will be necessary for many month or years till NxT becomes soooo popular. (hope weeks)
+But these guys has the problem that there capital is spitted on all there Nodes to attract more traffic.
+By linking the forging power to there local account to would be more attractive to create many VPS.
+It may possible to pay all your VPS with the forged NxT from your own forging pool....  
This is well applied decentralization.

[1714737152]

1714737152

[1714737152]

1714737152

[1714737152]

1714737152

[1714737152]

1714737152

[coolfish]

But the dollar's price is declining

[smartwart]

And lets combine one user his split-capital due to weighted VPS-Nodes to forge...
-Hammer-Feature-

We need to introduce measure that prevent everybody to forge @ one VPS because as the result will have this only one VPS. There will be no reason to own nxt node

Agreed. Need to have a parameter in web.xml to configure how many user accounts are allowed to forge on a node. Let the owner of the node decide that number in the config file.

 ahh, now I see....

[laowai80]

And lets combine one user his split-capital due to weighted VPS-Nodes to forge...
-Hammer-Feature-

We need to introduce measure that prevent everybody to forge @ one VPS because as the result will have this only one VPS. There will be no reason to own nxt node

Agreed. Need to have a parameter in web.xml to configure how many user accounts are allowed to forge on a node. Let the owner of the node decide that number in the config file.

 ahh, now I see....

The owner of the node can already block everyone from forging on his node with the AllowedUserHosts parameter, but why not make it a little more configurable, if it's not too much coding work. And display a 'No vacancies' message when people try to unlock their account if the node is full. Default parameter can be 'unlimited' of course.

This is beneficial for decentralization.

[EmoneyRu]

Then he will paste 100000000000 and we will have "only one VPS". It should be calculated based on uptime, connected peers, technical characteristics, etc

Why would he do that?

I'll do that. Forbid me (how?).

And why would everyone go to just one node?

Other users will have to give me some public key once, lay down and gain nxt on forging.
Why they should seek for another node if they are all the same?
If you'll create new crypto-currency will you setup your own forum or just come to the popular one?

Calculating it brings more bugs, why not just set it in the web.xml?

Solvable technical problem. Hire good programmers to do that.

[laowai80]

Then he will paste 100000000000 and we will have "only one VPS". It should be calculated based on uptime, connected peers, technical characteristics, etc

Why would he do that?

I'll do that. Forbid me (how?).

And why would everyone go to just one node?

Other users will have to give me some public key once, lay down and gain nxt on forging.
Why they should seek for another node if they are all the same?
If you'll create new crypto-currency will you setup your own forum or just come to the popular one?

Calculating it brings more bugs, why not just set it in the web.xml?

Solvable technical problem. Hire good programmers to do that.

Why forbid you? Please do that, 'unlimited' should be there by default. But if someone wants to restrict, it's a nice paremeter to have, along side with the max number of connected peers and other settings.

[kunibopl]

Brainstorming

I'd like to modify this concept a bit in a universal way.
I'd like to lock a portion of my account (up to the whole account)
I want let's say invent a turtlecoin with value xx_NXT, grant a specific account (other or mine) the right to pull this turtlecoin if he sends a password and define a timeframe during this has to be done. after the timelimit the turtlecoin becomes NXT again.
During the timeframe the turtlecoin is locked for me.

this way the NXT-client could print a QR-Code with the generated password, I go to the petshop and the owner can pull the turtlecoin with it.
-> I get the turtle and both are happy  

this is of course only one application for this feature. of course turtlecoin can be replaced by amout xx NXT.

another idea: it wouldn't be hard to implement an escrow this way.

I wanna sell a turtle. buyer sends me pass for turtlecoin, which I only can pull after turtle reached buyer succesfully.
if he doesn't confirm turtle reached him alive, the turtlecoin becomes invalid for me and him also and goes as NXT to a predefined social fund.
the buyer can trick me, pretending the turtle was dead, but he won't do this very often, because the network stores unsuccesful trades.

[Come-from-Beyond]

Brainstorming

I'd like to modify this concept a bit in a universal way.
I'd like to lock a portion of my account (up to the whole account)
I want let's say invent a turtlecoin with value xx_NXT, grant a specific account (other or mine) the right to pull this turtlecoin if he sends a password and define a timeframe during this has to be done. after the timelimit the turtlecoin becomes NXT again.
During the timeframe the turtlecoin is locked for me.

this way the NXT-client could print a QR-Code with the generated password, I go to the petshop and the owner can pull the turtlecoin with it.
-> I get the turtle and both are happy  

this is of course only one application for this feature. of course turtlecoin can be replaced by amout xx NXT.

another idea: it wouldn't be hard to implement an escrow this way.

I wanna sell a turtle. buyer sends me pass for turtlecoin, which I only can pull after turtle reached buyer succesfully.
if he doesn't confirm turtle reached him alive, the turtlecoin becomes invalid for me and him also and goes as NXT to a predefined social fund.
the buyer can trick me, pretending the turtle was dead, but he won't to this very often, because the network stores unsuccesful trades.

I like ur idea. The only exception - I would replace "turtle" with "girl".

[smartwart]

Then he will paste 100000000000 and we will have "only one VPS". It should be calculated based on uptime, connected peers, technical characteristics, etc

Why would he do that? And why would everyone go to just one node? Calculating it brings more bugs, why not just set it in the web.xml?

Transparent Forging will lead the user to jump directly to the nxt node which will forge nxt block.
This also leads to "self-fulfilling prophecy".

[Isildur23]

Can we lock any outgoing transactions until we receive a specific sum of Nxt (for example receive exactly 1637821 nxt)?

[NxtChg]

I wouldn't click at any of them if I don't know to what they are targeting. Now aliases for paranoids are useless

+1

[Isildur23]

Brainstorming

I'd like to introduce a concept of a new feature called Account Control. This feature will allow to do different things with ur accounts. For example, u will be able to set a lock on an account to prohibit any outgoing transactions until a special condition met (e.g. an incoming transaction from a predefined account). Another example is Pooled Forging, when an account leases its forging power to another account.

Please, post here what u would like to see in Account Control.

Can we set it so that outgoing transactions are enabled only in specific hours, or in some interval of time ( for example only between 11:30 p.m. and 11:50 p.m., or only on  1st January?)

[wesleyh]

I wouldn't click at any of them if I don't know to what they are targeting. Now aliases for paranoids are useless

+1

Will make some sort of popover that shows where it links to (in browser extensions)

[laowai80]

Transparent Forging will lead the user to jump directly to the nxt node which will forge nxt block.
This also leads to "self-fulfilling prophecy".

What would be the purpose of this jump? It's not the node that forges, it's the particular unlocked account that forges. The node is just a platform to forge.

[utopianfuture]

I wouldn't click at any of them if I don't know to what they are targeting. Now aliases for paranoids are useless

+1

Most mainstream users are not paranoid. They just like what are friendly and easy to use. That is well established by some credible large scale surveys for users of Facebooks, whatsapp, snapchat etc.
Well you could see how easy savvy people here are falling for scams like Visa, Neon, shares etc.

[utopianfuture]

I wouldn't click at any of them if I don't know to what they are targeting. Now aliases for paranoids are useless

+1

Will make some sort of popover that shows where it links to (in browser extensions)

that would be perfect.

[EmoneyRu]

I wouldn't click at any of them if I don't know to what they are targeting. Now aliases for paranoids are useless

+1

Will make some sort of popover that shows where it links to (in browser extensions)

I know 2 implementations:

• Popover
• Replace

[ImmortAlex]

Brainstorming

I'd like to introduce a concept of a new feature called Account Control. This feature will allow to do different things with ur accounts. For example, u will be able to set a lock on an account to prohibit any outgoing transactions until a special condition met (e.g. an incoming transaction from a predefined account). Another example is Pooled Forging, when an account leases its forging power to another account.

Please, post here what u would like to see in Account Control.

Can we set it so that outgoing transactions are enabled only in specific hours, or in some interval of time ( for example only between 11:30 p.m. and 11:50 p.m., or only on  1st January?)

It start to looks like "account setup transaction". I like the idea:
1. Block all coins from spending.
2. Block some coins from spending.
3. Set blocking time.
4. Allow to send coins only to specified account.
5. Combine that settings, so in different time there can be different number of coins blocked.

[NxtChg]

Will make some sort of popover that shows where it links to (in browser extensions)

Blacklist of malicious aliases might be a good idea too...

[Come-from-Beyond]

Will make some sort of popover that shows where it links to (in browser extensions)

Blacklist of malicious aliases might be a good idea too...

Who will decide if an alias is malicious enough?