Author Topic: how to change between TITAN &NON TITAN?  (Read 3105 times)

0 Members and 1 Guest are viewing this topic.

Tuck Fheman

  • Guest
$   enable_raw

$    blockchain_get_account

Quote
"type": "titan_account",


 +5% thanks for the tip!

Offline karnal

  • Hero Member
  • *****
  • Posts: 1068
    • View Profile
Well, that confirms it.. unfortunately this is yet another example of outdated documention, as I am pretty sure about having done the necessary research and reading that TITAN would be there by default.


At this point I can no longer assume any documentation in our wiki is correct. This is cause for concern, since few amongst us actually have the time to go through the source code digging for how stuff works (and even fewer could actually do that).



Could someone knowledgeable on this topic explain:

- Whether my privacy has been completely compromised - ie, can anyone get the current balance and complete past history of my accounts

- Whether it is possible to convert the account to TITAN, and if yes, how to do so.

- The consequences of switching to TITAN at this point (ie, the privacy implications of doing so)


Thanks..
« Last Edit: March 18, 2015, 04:55:17 pm by karnal »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Ouch... :-[

Would you know how to confirm which account type it is, from the console?

Quote

$   enable_raw

$    blockchain_get_account donations.xeroc
{
  "id": 34349,
  "name": "donations.xeroc",
  "public_data": {},
  "owner_key": "BTS5XPmkBSDXnUNLpojrDReqaZSA7ouqRtX9XutF4hbhfraLsPr71",
  "active_key_history": [[
      "2015-03-01T18:18:40",
      "BTS89U1u1kHrxHCUTfEZG5XixNsYy9cVeEyawnzC9dom5duUvULit"
    ]
  ],
  "registration_date": "2015-03-01T18:18:40",
  "last_update": "2015-03-01T18:18:40",
  "delegate_info": null,
  "meta_data": {
    "type": "public_account",
    "data": ""
  }

}



Offline karnal

  • Hero Member
  • *****
  • Posts: 1068
    • View Profile
Ouch... :-[

Would you know how to confirm which account type it is, from the console?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
So the default account type is TITAN, when created from the GUI, yes?

At least it's the default in the CLI:
Quote
account_type (string, optional, defaults to "titan_account"):

but it seams that the web_wallet (GUI) uses public accounts as (fixed) default:
https://github.com/BitShares/web_wallet/blob/master/app/js/controllers/registration.coffee#L53

Offline karnal

  • Hero Member
  • *****
  • Posts: 1068
    • View Profile
So the default account type is TITAN, when created from the GUI, yes?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
can I change public account  to  TITAN account?
not yet .. but afaik 0.8.0 will bring the feature to modify meta_public_data

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
can I change public account  to  TITAN account?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Puh .. wouldnt have made any sense .. at least to me ..

So whats the motivation to write the contrary into the cmd drscription? Anyone?

Offline jamesc

I agree with arhag .. we need memos for public accounts too ... that way btc38 can proof solvency and let costumers tranfser funds to a NONTITAN account
had updated the code let no-titan account can received memo ?

Public accounts can receive encrypted memos.  The wallets support this already.

Offline BTSdac

  • Hero Member
  • *****
  • Posts: 1219
    • View Profile
  • BitShares: K1
I agree with arhag .. we need memos for public accounts too ... that way btc38 can proof solvency and let costumers tranfser funds to a NONTITAN account
had updated the code let no-titan account can received memo ?
github.com :pureland
BTS2.0 API :ws://139.196.37.179:8091
BTS2.0 API 数据源ws://139.196.37.179:8091

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
  "meta_data": {
    "type": "titan_account",
    "data": ""
  },

meta_data can be update or not?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I agree with arhag .. we need memos for public accounts too ... that way btc38 can proof solvency and let costumers tranfser funds to a NONTITAN account

Offline arhag

  • Hero Member
  • *****
  • Posts: 1214
    • View Profile
    • My posts on Steem
  • BitShares: arhag
  • GitHub: arhag
OMG
public accounts do not receive memos and all payments are made to the active key
&blockchain_get_account_public_balance  can show the balance

Yup  :(

Although it seems wrong to me that public accounts do not receive memos. There is no reason this has to be the case (encrypted memos are doable with transfers to public accounts without requiring the public account to scan the blockchain). Can I get confirmation from devs on this?

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
GUI create new account that is  public_accoun   
consolo  create new account that is    ttitan_account

OMG
public accounts do not receive memos and all payments are made to the active key
&blockchain_get_account_public_balance  can show the balance




Code: [Select]

>> help wallet_account_register

Usage:
wallet_account_register <account_name> <pay_from_account> [public_data] [delegate_pay_rate] [account_type]   Updates the data published about a given account
Updates the data published about a given account

Parameters:
  account_name (account_name, required): the account that will be updated
  pay_from_account (account_name, required): the account from which fees will be paid
  public_data (json_variant, optional, defaults to null): public data about the account
  delegate_pay_rate (uint8_t, optional, defaults to -1): -1 for non-delegates; otherwise the percent of delegate pay to accept per produced block
  account_type (string, optional, defaults to "titan_account"): titan_account | public_account - public accounts do not receive memos and all payments are made to the active key

Returns:
  transaction_record

aliases: register



Code: [Select]
>> help blockchain_get_account_public_balance

Usage:
blockchain_get_account_public_balance <account_name>                                                  Get the account record for a given name
Get the account record for a given name

Parameters:
  account_name (account_name, required): the name of the account whose public address you want

Returns:
  account_balance_summary_type