[API] Questions about public memo, vote_ids, key-value storage

[xeroc]

Great.. is it only active_keys that have permission to change memo_key? i.e. nothing can go wrong by sharing that private key?

I think you'll need the owner key to change any keys.
All the memo key can do is decode the memo (unless it's the same keys as the
owner/active key!!!)

Would it be possible to have a BLANK memo key? That could at least be a blockchain-level signal to would-be memo senders that the contents will not be encrypted..

No idea .. give it a try.

Ok, I managed to update the memo key using the GUI wallet. What's not clear to me is how to feed it the private key..
the wallet shows no indication of incoming memos now.

I can't find any method that updates account keys (owner, active, memo) in the wallet API..
http://docs.bitshares.eu/namespaces/wallet.html

The only one is update_witness which allows you to set the signing key.

I agree key-value store should be added ASAP... devs, any thoughts as to how this could be implemented?

I am pretty sure they have a worker proposal for something similar in mind ..

Hmm..........

Is this memo issue still in need of a hardfork?
i'm not github savvy, but this screen tells me that we have 5 upcoming hardforks?
https://github.com/cryptonomex/graphene/labels/hardfork

I'm not sure about those hardforks. Only one of those looks like a recent issue.. not sure if the others are still relevant.

I don't think the memo issue needs a hardfork.. maybe just a new API method:
set_memo_key(string account_to_modify, string new_memo_key, bool broadcast)

Ideally, new_memo_key could be a blank string and would allow for plaintext memos.

I agree .. could you please add a github issue to this?

In the mean time.. I think the web Wallet allows for changing the memo key

[roadscape]

a few places left, maybe add that to the docs too?
https://github.com/cryptonomex/graphene/labels/docs

Sorry ken, not sure what you mean?

[kenCode]

a few places left, maybe add that to the docs too?
https://github.com/cryptonomex/graphene/labels/docs

[roadscape]

Great.. is it only active_keys that have permission to change memo_key? i.e. nothing can go wrong by sharing that private key?

I think you'll need the owner key to change any keys.
All the memo key can do is decode the memo (unless it's the same keys as the
owner/active key!!!)

Would it be possible to have a BLANK memo key? That could at least be a blockchain-level signal to would-be memo senders that the contents will not be encrypted..

No idea .. give it a try.

Ok, I managed to update the memo key using the GUI wallet. What's not clear to me is how to feed it the private key..
the wallet shows no indication of incoming memos now.

I can't find any method that updates account keys (owner, active, memo) in the wallet API..
http://docs.bitshares.eu/namespaces/wallet.html

The only one is update_witness which allows you to set the signing key.

I agree key-value store should be added ASAP... devs, any thoughts as to how this could be implemented?

I am pretty sure they have a worker proposal for something similar in mind ..

Hmm..........

Is this memo issue still in need of a hardfork?
i'm not github savvy, but this screen tells me that we have 5 upcoming hardforks?
https://github.com/cryptonomex/graphene/labels/hardfork

I'm not sure about those hardforks. Only one of those looks like a recent issue.. not sure if the others are still relevant.

I don't think the memo issue needs a hardfork.. maybe just a new API method:
set_memo_key(string account_to_modify, string new_memo_key, bool broadcast)

Ideally, new_memo_key could be a blank string and would allow for plaintext memos.

[kenCode]

Is this memo issue still in need of a hardfork?
i'm not github savvy, but this screen tells me that we have 5 upcoming hardforks?
https://github.com/cryptonomex/graphene/labels/hardfork

[xeroc]

Great.. is it only active_keys that have permission to change memo_key? i.e. nothing can go wrong by sharing that private key?

I think you'll need the owner key to change any keys.
All the memo key can do is decode the memo (unless it's the same keys as the
owner/active key!!!)

Would it be possible to have a BLANK memo key? That could at least be a blockchain-level signal to would-be memo senders that the contents will not be encrypted..

No idea .. give it a try.

I agree key-value store should be added ASAP... devs, any thoughts as to how this could be implemented?

I am pretty sure they have a worker proposal for something similar in mind ..

[roadscape]

1) you can set a new memo key and release the wif key .. not sure you can post unencrypted but may be possible somehow. i dont thonk you can prevent anyone from sending anything to you

Great.. is it only active_keys that have permission to change memo_key? i.e. nothing can go wrong by sharing that private key?

Would it be possible to have a BLANK memo key? That could at least be a blockchain-level signal to would-be memo senders that the contents will not be encrypted..

2) you got it right .. afaik first digit defines which group to vote and second is id ..
I dont know of an api that does this already .. but should be added asap

3) i dont know (yet)

I agree key-value store should be added ASAP... devs, any thoughts as to how this could be implemented?

Thanks xeroc

[xeroc]

2) you got it right .. afaik first digit defines which group to vote and second is id ..
I dont know of an api that does this already .. but should be added asap

3) i dont know (yet)

[xeroc]

1) you can set a new memo key and release the wif key .. not sure you can post unencrypted but may be possible somehow. i dont thonk you can prevent anyone from sending anything to you

[roadscape]

1) Is it possible to have non-encrypted memos? Can an account be configured to receive only public memos?

2a) What's the format of vote_ids? 0:11, 1:27, 2:65, etc. Does each votable object have a unique vote_id? Is the first number a namespace and second number an incrementing id?

2b) Is there a method to get a list of accounts that specify a specific proxy? (And each account can only specify one proxy right?)

3) Is it in any way possible to implement a key-value store in the current version of Graphene?

Thanks