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

Basically, every time there's a transaction in the network, a fraction of the fee would be sent to a designated NXT account. If there's a lot of transactions this would add up to a nice amount over 30 days or so. Basically this would be awarded like a lottery every month to a random Nxter who ran an open client that month. The question is whether there's any way to verify if someone had been forging during the time period to be eligible. Maybe the reward would go out on a random day/time so that no one would know when it's coming and therefore be motivated to always be running an open client.

I'm just trying to think of ways to motivate people to forge when there's not much incentive to do so if you don't have a lot of stake.
This system would make forging akin to owning a lottery ticket. The odds would be somewhat low to win, but reward high enough to encourage participitation.

so this is your  original Allowed.userhost ? code :

a great idea

would love something like this.

Instead of leaving a browser page open, you can always see the current stats of your NXT, etc. just by looking in the taskbar.

Yes, of course .

Here is a really bad mock up (I'm no developer). Do you get the idea, my Nxters? Wouldn't you (and others) love this tool which would actively secure the Nxt network? Lightweight, unobtrusive. Like the dropbox app.

It's just this particular coin that can be mined.
It's not inherent in the system.

Would mining be needed for coins created on the exchange? I thought you could just "create" assets.  

did you have  separated  them with a comma?

Yes, we all have to wait when someone forges a block.

Does someone have the same problem on >=0.8.0 ?
If i put some ip address in nxt.allowedUserHosts i cannot connect from it to my node

Hi ,
 Can you wait a couple of minute ? I will send you 20k TestNxt ...

we need to wait for blocks to start forging.

Can someone please send some test Nxt my way?

16788579025215779162

Thank you!

PLEASE, I need testnxt 18232225178877143084
I want to debug while the code is fresh in my mind

I can think of several reasons, one example is if the coin needs to receive data via AM. It would then have to be part of the NXT network to be able to get the AM data.

Another reason that is just for security reason is to verify the total number of coins in circulation. It needs to match the total mined. until we get multisig in NXT, there is the possibility that the accounts that are holding the issued but unreleased coins will release some extra, especially when there is a nice market to sell it to. Since there is nothing I can think of that will stop that, the plan is for all the nodes to actively reconcile the total balances and if it doesnt add up properly, alarms and a snapshot of the current account balances are made. Then if the problem cant be resolved, everybody simply redeems their snapshot balance for a replacement Asset, and resumes without any real harm done.

The only harm would come to the one who broke the trust by trying to sell off what they were supposed to only release to the miners. Whatever coins they were able to pilfer wont be worth that much since it will be obsolete. Also, I think we can have part of the alarms to be canceling any outstanding orders the miners had on the AE. Anybody that is trading in these NXTcoins is advised to be running the alarm bot. So not elegant, but I think practical solution to not be able to create coins only when they are mined.

You can imagine how elaborate all this will be, all requiring access to the latest block. NXTcoin miners will secure the NXT network, I am pretty sure of this.

James

With DACs, isn't it possible to make a truly decentralized botnet that can't be shutdown? This "pool" would consist of many, many computers connected to it, each one leasing their forging power to the botnet. CPU power and bandwidth would be the total sum of all the connected users... which would be literally unlimited for our purposes. Also, the botnet can have redundancies (such as there are always 3 random computers sending the same information to make sure one of them is not malicious). With the penalty system, this large network with a large number of accounts will function normally. In fact, the penalty system would serve as a balancer - if one pool generates too many blocks compared to other pools, it's power will eventually be brought inline with other pools.

In fact, we can even build a DAC on-top of the DAC, that will automatically find the best pool for the user (it's priority would be to make sure there are always X number of competitive pools).

We can call this system: Skynxt.

Ahahah 

JeanLuc

Could you please add nxt.util.Logger.removeMessageListener and nxt.util.Logger.removeExceptionListener?

Thanks!

@JL:
Nice debug message.