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

I know, I know. And we know that

What was the error message in the console?

Peercover has completed manually fixing all the transactions.
To my knowledge, only three slipped through the cracks.
They are running 0.5.3 now, so hopefully it will remain in fully automated mode.

HOWEVER, I have been advised that for the next week, they won't be able to manually reconcile transactions. IF the NXT server crashes, you will have to wait until next week. I know this is not exactly comforting, but the NXT that is already on deposit can be freely traded without any fees or commissions. All the trades are done via the rippled servers, the only thing affected is the automated deposit/withdraw process for NXT.

Please be patient.

If you really, really need to get your NXT withdrawn or really really want to deposit your NXT, I can personally handle transactions of up to 10000 NXT. Just PM me.

I really hope we can all be patient as peercover regroups to deal with things. As long as 0.5.3 server doesn't hang, all is good.

James

Bug report:

Registered alias via alias.html
Filled fields. Pressed button. Button disabled. Wait. Wait. Button enabled. No text in bottom text field appeared.

What should I do?

Some things in life are better left with an air of mystery about them.

Bug report:

I have a bug when sending out money, twice in a row. The transactions still went though but the server stopped working and the send money command never moved to "money is sent" stage.

I took the liberty and compile the current state of the discussion.
This should make it easier to continue discussing separate aspects more in detail.

If I you all feel I lost some global point, please try to explain it with regard to concept integration.
I will separate the topics "Account Control" and "Forging Pools" to simplify keeping the overview.



Pooled Forging

Features:

+ account leases its forging power to another account

Short description of the Forging Pool Concept:

A particular unlocked account is able to link to a Node to provide his forging power.
If the Node has fored a Block, the forged NxT become splitted based on defined contract parameters, to all Forging Clients. This increase the individual forging reward of smaller accounts.
User are running hallmarked VPS Nodes could focus the forging power of all separate accounts.


Topic headlines for further discussions:


Configurable number of allowed Forging Clients to the Node.

+ parameter in web.xml to configure the number of allowed Forging Clients

+ When user link their account to the node, check against how many users are already forging on that node,
allow to unlock if the number is less than AllowedForgingUsers in web.xml
- and if it's equal to that parameter, display 'Node forging capacity is full' or something like that.

+ Limit number of allowed Forging Clients to prevent less number of big Monopools.    
Result of one big Monopool would be the same as all Clients are forging by her self.
Possible drawback would be Network architecture.


Forging Clients Contract Parameters
   
+ NxT amount, uptime, connected peers, technical characteristics, penalty.          
More help to the network - more abilities?

+ 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".

+ If we know the Node hwo will forge next Block we could link our account of    this Node for participation.
This assumes the rewards from participation are higher than possible contractual penalties for leaving a Node immediately,          after the Block was forged.
   
+ Distribution of forging reward by global contract parameters (protocol level) or individual contracts for each forging pool or hybrib approach?

+ Forging Clients paying Pool Commission to Forging Node?
   
+ Create a competitive marketplace for forging power.
Auctioning of my forging lease to the highest bidder; one-off, or similar to Amazon's "spot price"
where if someone bids higher whilst my forging power is leased to one party the lease automatically gets transferred to the new highest bidder


Link one Account to multiple Nodes

+ Different Pools, different pool profitability.
So split your account and into separate Forging Clients and link them to different Forging Pools.

Can we (core developers, client and tools developers) agree to use this as our main API documentation resource and keep it up to date together?

Also this is a by-design feature.

And all transactions were instantly confirmed by the god!

I would consider that to be morally wrong, at least trying to crack private keys for weak passphrases.  However, the hiberNXT on the other hard where there are no published public keys are another story.

This is called "блaт"

This is her photo - CLICK.

That's right.

Do copy the old .bak files to the new client directory and rename to .nxt files. Don't copy the old .nxt files to reuse.

It's my experience.

admin worked thanks all

I took the liberty and compile the current state of the discussion.
This should make it easier to continue discussing separate aspects more in detail.

If I you all feel I lost some global point, please try to explain it with regard to concept integration.
I will separate the topics "Account Control" and "Forging Pools" to simplify keeping the overview.



Account Controll

Features:
+ set a lock on an account to prohibit any outgoing transactions
+ definition of rules for unlocking the account

Short description of the Account Controll Concept:

Account Control feature will allow to set a lock on an account,
to prohibit any outgoing transactions until a special condition or event met.


featured posts:


+ I want a way to protect/secure/limit the withdrawal of my coins.[/li][/list]

+ Block outgoing transactions by pushing some public key, associated with account, to blockchain, and unlock with corresponding  
private key. (allows forging and doesn't requires to create another account)
From user's point of view it will be just password, blocking you account from spending money.

+ The locked account can be a saving account.
Or it could be used as an escrow monitored account as the escrow account is the predefined account.

+ It must be able forge or this feature have no meaning.
Option to allow outgoing transaction only if the account receives a transfer in from another account specified,
so that I can have a small account with 2-3nxt that can unlock my investment account (trigger account?)

+ Assign an automatic payment on any date. For example, if I have to constantly make payment for some days. (automatize periodical paymants?)

+ API request to start forging automatically after just another nxt-client failure.
Request should accept key that differs from secret pass-phrase.
Key shouldn't be kept in secret

+ Set 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.

+ I'd like to see spending limits.
For example so that I could only spend a maximum of 100 NXT/day from an account.
Trying to steal this account would be less profitable.

+ Nxt transfer, Alias selling and buying prohibition until a special condition met.
But hackers could probably register, when the special condition happens.


Questions:

Can a locked account forge ?        - Yes

Her sister is probably 40 year old but she might suit you fine 

And all transactions has 0 fee!

yes I also noticed that at the same time my problem started to occur, that when clicking on PMs here in BCt.org that it no longer goes directly to the PM