Author Topic: BitShares Faucet  (Read 6284 times)

0 Members and 1 Guest are viewing this topic.

Offline kenCode

kenCode@Agorise
Matrix/Keybase/Blurt/Hive: @Agorise
Session: 0525c95e7f37dca6e29ac84fe7030f0bc5f8bcd564207f03c893e47d2a381a2337

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
why would a SUBACCOUNT not be transfered as is? That doesn't make too much sense to me ...

Offline valzav

  • Sr. Member
  • ****
  • Posts: 294
    • View Profile
Created issue for this https://github.com/bitshares/web_services/issues/26
Not sure it makes sense to change anything at this point - in 2.0 faucet would be transparently integrated with web wallet so users won't ever see this form.

Offline kenCode

I am creating a new sub-account in my kencode wallet.
To Register that new child account, I'd like to use the faucet to avoid the new "bts-" naming schema.
 
On the faucet page (https://faucet.bitshares.org/) it says Account Name, Public Key and Owner Key.
 
Could we make that a bit more specific, like this:
 
Account Name to Register
New Account's Public Key
Owner's Public Key
 
Assuming the above is correct, I think that would make the 3 fields more obvious.
Please and thanx :)
kenCode@Agorise
Matrix/Keybase/Blurt/Hive: @Agorise
Session: 0525c95e7f37dca6e29ac84fe7030f0bc5f8bcd564207f03c893e47d2a381a2337