Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - roadscape

Pages: 1 ... 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 ... 64
376
Technical Support / Re: [API] Questions about public memo, vote_ids, key-value storage
« on: October 26, 2015, 05:21:52 pm »
Quote from: xeroc on October 26, 2015, 07:17:43 am
Quote from: roadscape on October 26, 2015, 03:00:37 am
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!!!)

Quote
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.

Quote
Quote
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..........

Quote from: kenCode on October 26, 2015, 12:26:34 pm
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.

377
Technical Support / Re: [cli_wallet] update_asset - how to use?
« on: October 26, 2015, 04:55:18 pm »
The wallet pays fees in BTS by default, but the GUI pays for fees using the BitAsset that's being transferred (currently there is no option to pay with BTS from GUI, but it will be implemented).

The thinking is that most future users will not care about core tokens.. they have a wallet with just USD/CNY/EUR in it and pay all fees with that.

378
Technical Support / Re: GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
« on: October 26, 2015, 06:34:24 am »
The export format is just a "minimal" version of the (encrypted) wallet, which is why you don't need to have your wallet unlocked when you export the keys. The keys file is as safe as the locked wallet itself.. not that I'd recommend sharing it

379
Technical Support / Re: [API] get decoded memo?
« on: October 26, 2015, 04:22:31 am »
The easiest way is to use get_account_history, which includes decrypted memo.

Yeah would be great to have a specific method for this.. I don't believe one exists yet.

There's xeroc's python code for encrypting/decrypting memos:
https://github.com/xeroc/python-graphenelib/blob/master/graphenebase/memo.py

380
Technical Support / Re: [API] Questions about public memo, vote_ids, key-value storage
« on: October 26, 2015, 03:00:37 am »
Quote from: xeroc on October 24, 2015, 07:55:13 pm
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..

Quote from: xeroc on October 24, 2015, 07:56:35 pm
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 :)

381
Technical Support / Re: [cli_wallet] update_asset - how to use?
« on: October 25, 2015, 10:06:12 pm »
I believe core_exchange_rate is the fee pool exchange rate, and it's used to calculate fees when they are paid in bitassets as opposed to BTS.

382
Technical Support / Re: [cli_wallet] reserve_asset throws unexpected exception
« on: October 24, 2015, 05:03:15 pm »
It appears either the API or documentation have it mixed up..

Flip the asset and amount, and it works:
reserve_asset monsterer METAFEES 0.1 true

@xeroc any insight into this?
http://docs.bitshares.eu/namespaces/wallet.html
reserve_asset(string from, string amount, string symbol, bool broadcast)

383
General Discussion / Re: How can we help BTC38? eg. falling price
« on: October 24, 2015, 04:31:23 pm »
Quote from: fuzzy on October 24, 2015, 04:11:40 pm
You know what is cool?  All the shady exchanges that don't sufficiently back their holder's tokens are now starting to be called out by NOT joining bitshares :P

 +5%

Quote from: habeler on October 24, 2015, 04:15:37 pm
Quote from: Empirical1.2 on October 24, 2015, 03:52:38 pm
Apparently an issue might be that they don't have all the BTS they're supposed too.

Quote from: alt on September 12, 2015, 04:26:19 pm
titan account will lost privacy protect  when upgrade to v2.0.
btc38 claim they have 363,130,741.49991 BTS, but  there are only 228,449,248 BTS in their cold wallet. they refuse to public all reserve because they say it's not security.
guess what will happen at BTC38 when upgrade to v2.0?

That makes no sense. If they are short they would have been buying big and that would have held up the prices. They can not expect to ride it out for ever, sooner or later they will have to add BTS and they know that.

If alt's numbers are right, they're $500,000 short.. if they bought $10k per day, it would take about 2 months (at current prices) to make up the difference.

384
Technical Support / [API] Questions about public memo, vote_ids, key-value storage
« on: October 24, 2015, 07:41:21 am »
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 :)

385
Technical Support / Re: GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
« on: October 23, 2015, 05:12:53 am »
Much needed, thanks!! +5%

386
Follow My Vote / Re: FMV will be going to WEB SUMMIT 2015! !
« on: October 23, 2015, 04:39:09 am »
Nathan Hourt is Co-Founder & CTO.. they must be up to something  :)
https://followmyvote.com/team/

387
Technical Support / Re: Network Security Question
« on: October 22, 2015, 10:57:08 pm »
If witnesses are signing blocks on more than 1 chain, any number of bad things could happen, including your scenario.

This is why we need to see to it that going forward our auxiliary utilities grow decentralized.. monitoring/failover, price feeds, etc are all susceptible to horrific failure if everyone uses the same service/codebase. Diversification of strategies mitigates the risk by ensuring that there is never consensus on a specific failure mode.

If double-signing is 100 times worse than missing a single block, then it's better to miss 2.5 hours of block production than to double-sign. That's why I'm not in a rush to automate this.

Ideally, it would be easy to identify double-signers so they can be informed of the risks (and fired for repeat offenses).
This would be the community's job, so hopefully someone builds a "fork explorer" tool into the next bitsharesblocks :)

388
Technical Support / Re: cli command for transaction history
« on: October 22, 2015, 07:06:05 pm »
get_account_history nathan 10

389
General Discussion / Re: Let's Lower Trading Fee
« on: October 22, 2015, 04:46:23 pm »
Quote from: luckybit on October 22, 2015, 03:51:40 pm
The market isn't going to come back with zero fees. It's not going to be a market until you actually do some marketing. I don't see any marketing, no banner ads, nothing. Of course the market is going to be dead if people cannot import their keys. I can't even import my keys so it's not my fault that the market is dead and if hundreds of others are in my position it's not their fault.

 +5%

Also.. a nice thing about a public blockchain with tunable parameters is that anyone can perform analytics and create compelling data-backed arguments for optimal price points. What this means is that in the long run we *will* have very optimized and competitive pricing. But until people can import their keys and the rest of the exchanges upgrade to 2.0, we're not going to see any activity or actionable data.

I've spent 35,000 BTS in fees since launch just between upgrading accounts and witness reg. Maybe I'm just getting desensitized  :)

390
Random Discussion / Re: Help for Windows users and Exchanges that are having a hard time migrating
« on: October 22, 2015, 04:11:58 pm »
Quote from: xeroc on October 22, 2015, 03:09:13 pm
Calm down guys.. Hes intension may have been good .. the issue is you are considered rather "new" to this community and it's common practice to warn everybody about potential risks involved with downloadable blobs from unknown or not yet trusted individuals .. I am sure you understand that ..

 +5%

Pages: 1 ... 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 ... 64

Page created in 0.027 seconds with 23 queries.