Topic: | Nxt | Blockchain Platform | Proof of Stake | Official - page 333. (Read 941287 times)

nxtexplorer.com update

some enhancements like:

last 720 block forging account distribution/summarize -> http://nxtexplorer.com/nxt/nxt.cgi?action=150
hibernxt/darknxt -> http://nxtexplorer.com/nxt/nxt.cgi?action=30&switch=20
added top lessors with total nxt per account and total leased balance -> http://nxtexplorer.com/nxt/nxt.cgi?action=30&switch=8
(currently 158,691,597 NXT from 293 lessors are accumulated into 56 accounts)

and some more personal account views.
please see full list here: https://nxtforum.org/news-and-announcements/nxtexplorer-update/msg58279/#msg58279

nxtexplorer.com update

some enhancements like:

last 720 block forging account distribution/summarize -> http://nxtexplorer.com/nxt/nxt.cgi?action=150
hibernxt/darknxt -> http://nxtexplorer.com/nxt/nxt.cgi?action=30&switch=20
added top lessors with total nxt per account and total leased balance -> http://nxtexplorer.com/nxt/nxt.cgi?action=30&switch=8
(currently 158,691,597 NXT from 293 lessors are accumulated into 56 accounts)

and some more personal account views.
please see full list here: https://nxtforum.org/news-and-announcements/nxtexplorer-update/msg58279/#msg58279

I'm getting a "New Beta" notification in my NXT client. If I update, will that give me access to MGW to test?
Mostly I'd like to see the look and feel of it to put together a film script.

I'm ready to implement the next step to Transparent Forging. Usually I do it silently but this time its consequences will be noticeable, so I'd like to hear feedback of the community.

What I'm planning to do:
1. Disable retargetting (the base target will be set to 100%)
2. Enable Time Warp effect (the first forger in the queue will be allowed to generate the block in 60 seconds, next one - in 75 sec, then 90 sec and so on adding 15 sec every time)
3. Enable penalty (an account that skipped its turn to forge a block will be put out of business for the next 1440 blocks)
4. Enable normalization of forging power (difficulty of blocks will be multiplied by 1'000'000'000/X, where X is total forging power of the system)

#1 is an atavism, we don't really need it if #2 is active.
#2 is for convenience, why should we wait 10-30 minutes if the next forger is already known.
#3 is to incentivize forging, it's also a part of 90% protection.
#4 is necessary for security, coz #3 may "disable" some active forgers.

when can we see the pump?

Buff!! This Automatec Transaction thing is way complicated...

Is there a simple explanation for the coding-average-joe?

The only time you should need your password is when creating a transaction. At which point the client already knows the account number, so it can verify they match and explain exactly what has happened if they don't. If you must, at this point have the option to remember the password for the session.

Ideally the login screen would remember the last used account number, so you wouldn't actually have to type it. Better still, remember the last few accounts and let the user pick one from a list. Better still, have the screen show useful summary information about the known accounts right from the start: individual balances, plus total balance for all accounts, etc. Most people have more than one Nxt account so multiple accounts ought to be easier to manage.

For all to think about it and to support the AT Team.

I will in fact revise this idea

Remove  "Remember password during this session" totally

and just have   "pin number for the session" (only 4 to 6 numbers allowed)

Concerns and issue; compiled from a discussion with JL.

The team around AT needs to answer these questions during the testing period of AT.



0) Problem is not to achieve something with AT, but how to restrict AT scripts to avoid inconsistent results: cf. below


1) We need to make it safe in certain ways:
 - restricting AT scripts - transactions validation?
 - can a script create other scripts (viruses)?
 - access on core resources - querying them
 - using core capabilities - like methods of the Account class and so on

2) Scalability:
 - re-executing the script on every node?
 - better of avoiding it?
 - some sort of easy proof that the script was executed correctly?

3) Code complication
 - minimizing the core code
 - if script is using internal core methods, core modifications will be necessary everywhere -> first step: using regular transactions, second step: creating custom transactions, third step: introducing custom objects

4) How to start a script?
 - by transaction?
 - by height trigger?
 - by what else?

5) Scientific research done?

6) How to do debugging?
 - Who called what when and why?
 - different languages in use

7) How to do updating a AT script?

How to migrate running/active AT scripts once the underlying program found flawed and a new version is/will be deployed?

9) Atomicity
 - Are scripts atomic?
 - How to achieve atomicity?
 - How to split up atomicity within one script?
 - When is the output of a script accepted, i.e. changes balances and the like? (turing complete -> Halting problem etc.)
 - rollback necessary?

10) What is the output of a script?
 - a sequence of regular Nxt transactions?
 - using custom transaction types?
 - directly manipulating the Core Objects like Account, Aliases, Orders etc. etc.

11) What is the input of a script?
 - block headers?
 - confirmed transactions?
 - raw transactions?

12) When calling internal methods like DigitalGoodsStore.deliver(), how to we enforce rules that are set by the corresponding transaction type?


That is it for now. Keep you updated.

Spot the - Ooopps...... http://cryptoanalytics.trade/analyst-ratings/

I'm getting a "New Beta" notification in my NXT client. If I update, will that give me access to MGW to test?
Mostly I'd like to see the look and feel of it to put together a film script.

Spot the - Ooopps...... http://cryptoanalytics.trade/analyst-ratings/