Could someone send me ~21XTS to register a new delegate? Thanks! 

send to "wackou" (registered on the blockchain as XTS8SCY7ZFAK72uL1jQjWtchDRvf3nz1m7rkDeEn818WRdZiqEo5f)

btw, I successfully imported my keyhotee founder account/key (great!), however there are no funds associated with it. I thought there would be one day of AGS (and hence some BTS) for keyhotee founders, or did I miss something?

wallet_import_armory should work now.  (actually Issue #90 says it needs testing, care to help test?)

Armory import seems not implemented at all yet... Tried it with actual values, as well as random values, gives OK all the time

>>> wallet_import_armory
wallet_filename: /this/file/does/not/exist
passphrase:
account_name: well, this is not an account
OK

A few things:

>>> wallet_withdraw_delegate_pay init-delegate-82 wackou 100000 "test withdraw"
10 assert_exception: Assert Exception
delegate_account_record->delegate_info->pay_balance >= (amount_to_withdraw + required_fees.amount):
    {"delegate_account_record":{"id":82,"name":"init-delegate-82","public_data":null,"owner_key":"XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg","active_key_history":[["20140618T180300","XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg"]],"registration_date":"20140601T000000","last_update":"20140601T000000","delegate_info":{"votes_for":83832250149,"votes_against":0,"blocks_produced":177,"blocks_missed":183,"pay_balance":10980294,"next_secret_hash":"f0cebbf2a660d2ecd7c3b8483e9928b504e2e212","last_block_num_produced":20893},"meta_data":null}}
    th_a  wallet.cpp:1363 withdraw_delegate_pay

    {"delegate_name":"init-delegate-82","amount_to_withdraw":100000}
    th_a  wallet.cpp:1404 withdraw_delegate_pay

    {}
    th_a  common_api_client.cpp:652 wallet_withdraw_delegate_pay

    {"command":"wallet_withdraw_delegate_pay"}
    th_a  cli.cpp:572 execute_command

In particular:
delegate_account_record->delegate_info->pay_balance = 10980294
amount_to_withdraw = 100000
required_fees.amount = not sure exactly how much, thought it was 10000

which means that this should be able to go through, no? Or is there a certain period of time during which the delegates cannot withdraw the xts on their account?

In any case, can someone send me some XTS to register a new delegate? Thanks!
wackou XTS8SCY7ZFAK72uL1jQjWtchDRvf3nz1m7rkDeEn818WRdZiqEo5f

And 2 more questions to end:
 - do you have the armory wallet import planned for soon? If not, I imagine there should be a way for me to export the private keys from Armory and import them as bitcoin(?) keys
 - how do I import my PTS wallet?

PSA: for people trying to get this to work on debian and getting import errors for keys, make sure that you compile with gcc 4.8, as gcc 4.7 doesn't work (compiles correctly but then crashes randomly or fails importing keys in weird places...)

VPS hosted at gandi.net
Location: Paris, France

Config (easily upgradable if necessary):
CPU: 2-core Xeon E5-2650L
RAM: 1G
BW: 100MB/s
OS: Debian stable + some libs from testing

Public keys:
wackou-delegate-1 XTS8Nycs16hWgGQTykcZ8n581scfBePSvyrxAWtfoLYBp4m6VqcCg
wackou-delegate-2 XTS5GfSidYreeUq4WCSEiEoFnmmCgJkDnGaXkPQDVPQJsrztKyCq3
wackou-delegate-3 XTS6sfrKvzeeo6P1Cz2eKusMRPEdWJhSYazJiikaXUizCd5o38oc5
wackou-delegate-4 XTS71xQ7RSg6w3Vbexe8gsQ27stzchhT9qR3o7PABF93rNn4zvJE2
wackou-delegate-5 XTS665TbeRTytMe8u3PusSPeUNUcdMDFke5g459NTU3RWfneafEWA

After every shuffle, the order of next 100 blocks' forgers is determined. So most of the delegates may have time to tear the node down for a while and relaunch it. At this time, another instance needs to be already pulled from GitHub and built. In fact, you may always need a 'left' instance and 'right' instance, just like a seesaw. The left instance and right instance can share the same data directory, which is ~/.BitSharesXTS by default.

Thought exactly the same thing Also, you don't really need to wait for a shuffle as the time between blocks is 30s and the client starts in much less than that, so you should have time to hot-swap an upgraded delegate at pretty much any time you want. You definitely need to have it built at that time already so you just need to bring it up. I'll probably write some (python or bash) scripts at some point to deal with that, if it seems that this is the way to go, I'll share them on github.

It is really as simple as having two nodes on the network (different data directories)... then lock one wallet and unlock the other to switch versions.  You can take down the locked version for an update and then bring it back up.

I'm not sure I understand everything here. Do you mean that a delegate can only sign blocks if its wallet is unlocked? So if I start a delegate and open a wallet, but don't unlock it with its password then it won't sign blocks? How can we deal with timeout for unlocking then? Does wallet_unlock accept a timeout of 0 meaning infinite time? Or did you mean open/close instead of unlock/lock?

Also, do I understand correctly that the IP of the delegate is not important as long as it is able to sign blocks in time, and that it is completely feasible to bring one down with an IP and another one up with another IP? That would be super awesome because it means it is possible to have a backup delegate node in a different location which can immediately be switched up if the first one fails.

yep, sent me some XTS to myself after setting trust level for a few delegates.

Unrelated, but I seem to have found another (seemingly minor) bug:

at first, I had registered wackou2 as a normal account, but then tried to upgrade it to a delegate, but using the wallet_account_register instead of wallet_account_update_registration.
This failed (because the account was already registered) but created a transaction anyway that has been pending since then (the fee has not been credited, though). Even after a blockchain rescan it is still there. I then later tried to upgrade it using the wallet_account_update_registration, which worked, but I still have the old one pending in the wallet.

>>> wallet_account_transaction_history
  #    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                   AMOUNT                 FEE          VOTE                                        ID
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1    892.0    2014-06-05T11:02:30 XTS8gUQbBB7Qevi4... wackou2                                             1,000,000 XTS               0 XTS           N/A  4e111ecf81c1b7700433183e42274fb9da9ff136
  2    902.0    2014-06-05T11:10:30 wackou2             wackou2             register wackou2                        0 XTS          10,001 XTS           N/A  f3fd0d12060d3d679558fc7d5deb16997000892d
  3    914.0    2014-06-05T11:21:30 XTS8gUQbBB7Qevi4... wackou2             呵呵啊哈哈                 1,111,111 XTS               0 XTS           N/A  86cf612424441627572874915884e0ffe6b54129
  4   1013.0    2014-06-05T12:44:00 XTS8gUQbBB7Qevi4... wackou2                                            50,000,000 XTS               0 XTS           N/A  87d30e30e56120367e1cdab5c182b1b13b1c614f
  5   pending   2014-06-05T12:46:05 wackou2             wackou2             register wackou2 as a...                0 XTS       4,324,117 XTS           N/A  367c95fce3db976f84a29aea978534610358310e
  6   1021.0    2014-06-05T12:50:00 wackou2             wackou2             register wackou-deleg...                0 XTS       4,324,117 XTS           N/A  74d7846eb57ac031943423f145de3599e8d4d1d0
  7   1093.0    2014-06-05T13:51:00 wackou2             brannigan           test send                      -1,000,000 XTS          10,000 XTS           N/A  677cfec362298eb03270b637b3df0e499f47dfc2
  8   1096.0    2014-06-05T13:53:30 brannigan           wackou2             send back                         100,000 XTS               0 XTS           N/A  fd70e7853d1f7a92e30ca3b80f454f7a15f70888
  9   1111.0    2014-06-05T14:07:00 wackou2             wackou2             update wackou2 as a d...                0 XTS       4,324,118 XTS           N/A  ff08ed23d8ff5786f392d2f0354447f2bd68100f

Also, is it better to report these type of issues here, while we're all looking at them in the heat of the moment, or on github, where it's easier to manage in the long run?