196
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.
197
General Discussion / Re: New BitShares (2.0) Website Feedback
« on: June 10, 2015, 09:13:54 pm »Github link now redirects to the old bitshares.org page? I really love the new design and information structuring, bring it back!
All links should not point to the new website. Old site is temporarily accessible at http://v1.bitshares.org/
198
General Discussion / Re: New BitShares (2.0) Website Feedback
« on: June 10, 2015, 09:12:28 pm »Big Money audience: "industrial-grade financial smart contract platform" is a great hook.
Top line of links/puffs though I would have thought should be "Decentralized Asset Exchange"; "High Performance and Scalability"; "Collateralized Bond Market". I don't know but whatever will ensure that the key audience is hooked.. they may not scroll down that webpage that looks like every other webpage unless there are enough hooks on first glance.
Reordered the features somewhat.
199
Technical Support / Re: Can't restore from json, need help
« on: June 10, 2015, 04:33:49 pm »Maybe a known issue .. onlx work around i know of would be to install a earlier version .. sth like 0.5.4 .. import the backup there and the upgrade to 0.9.2
Yes as xeroc said the best workaround is unfortunately to downgrade to this version: https://github.com/bitshares/bitshares/releases/tag/bts%2F0.5.3, import your wallet, then upgrade directly to 0.9.2. Make a new backup after confirming the upgrade to 0.9.2 was successful.
200
General Discussion / Re: New BitShares (2.0) Website Feedback
« on: June 09, 2015, 10:28:17 pm »
Will an asset price ticker or some kind of price information be on the home page to help reinforce that this is an actual exchange?
We hadn't planned on it, as the site is focusing on BitShares as a smart contract platform with many features, not just the exchange feature.
201
General Discussion / Re: New BitShares (2.0) Website Feedback
« on: June 09, 2015, 10:15:27 pm »What's the reason you guys chose to move the website to github hosting?
General simplicity of development, maintenance, and operations; and also anyone in the community can relatively easily contribute changes by submitting a pull request on GitHub.
202
General Discussion / New bitshares.org Feedback
« on: June 09, 2015, 10:10:42 pm »
https://bitshares.org/ has been replaced with the new BitShares 2.0 website hosted using GitHub pages at this repository: https://github.com/bitshares/bitshares.github.io
The old website will be kept temporarily online here: http://v1.bitshares.org/
All constructive feedback on the new site is appreciated.
Special thanks to cass, xeroc, robrigo, CryptoPrometheus, Chronos, and bytemaster for working so hard to build the new website.
The old website will be kept temporarily online here: http://v1.bitshares.org/
All constructive feedback on the new site is appreciated.
Special thanks to cass, xeroc, robrigo, CryptoPrometheus, Chronos, and bytemaster for working so hard to build the new website.
203
General Discussion / Re: Requesting volunteers to provide seed nodes
« on: June 08, 2015, 09:42:02 pm »I have had to change my seed node. I am no longer running 95.85.33.16:8764, I am now running 46.101.130.197:1776. I apologize for the inconvenience.
Updated: https://github.com/bitshares/bitshares/commit/7042d321bd1f4964d16197e864179f739f2e79b6
204
Technical Support / Re: Duplicate transaction on different Block
« on: May 21, 2015, 10:02:26 pm »
Did you base your code off of master branch? You should base your code off of toolkit branch as stated in the README in order to avoid all of the hardfork logic that is specific to only the BTS network.
206
General Discussion / Re: CoinCap.io- Realtime Market Data of All Cryptocurrencies, BitShares
« on: May 20, 2015, 08:47:43 pm »
Looks nice. Is this aiming to be a real-time, better version of coinmarketcap?
Will you be adding sources/information on how the Volume is calculated?
Will you be adding sources/information on how the Volume is calculated?
207
General Discussion / Re: Reconstruct memo info from a seed
« on: May 20, 2015, 05:15:02 pm »If we want to reconstruct the entire transaction history of an account, we need to decode the memos that were sent from us and the memos received by us. (The second ones are not a problem since we have all the necessary information to decode).
But, the reconstruction of the shared secret (used to encrypt the memo out) forces the client to keep a reference to the key used (child index of HD key, full ECkey, other).
If we can just store 4 bytes in the memo we can relieve the client from storing that references (since the reference will be in the blockchain) and will let reconstruct the entire history just from a seed.
This 4 bytes can be obscured/encrypted using skip32 or other mechanism.
It there any possibility to do this in the core?
I don't want to increment blockchain size since it will have a big impact on the long term, but can we give a new meaning to some memo fields?
@vikram
I believe we are planning to use a scheme like this for a future upgrade to BitShares. bytemaster or modprobe can confirm.
209
Technical Support / Re: Duplicate transaction on different Block
« on: May 20, 2015, 05:10:05 pm »
What is the output of the following commands?:
Code: [Select]
blockchain_get_block 601
blockchain_get_block 613
blockchain_get_block 756
210
General Discussion / Re: BitShares 0.9.2 Feedback
« on: May 19, 2015, 03:23:36 pm »I have some concerns about the bts/0.9.2 release as I do not see the code previously released to the dvs/0.9.x network for testing. It is my understanding that all code in BitShares will go through DevShares first for testing.
DevShares:
20 APR 2015 | Latest commit [1]
BitShares:
18 MAY 2015 | bts/0.9.2 [2]
04 MAY 2015 | bts/0.9.1
24 APR 2015 | bts/0.9.0
Request:
Please help me understand the decision process used to release the bts/0.9.2 code into the BitShares network.
References:
[1] https://github.com/BitShares/DevShares/commits/master
[2] https://github.com/BitShares/bitshares/commits/master
DevShares is a tool to help prevent problems with BitShares upgrades. It is not a perfect tool, and cannot help with some parts of the upgrade process because the DevShares network has a completely different state from the BitShares network, and hardforks happen at different times between the two networks. So we use this tool at our discretion, but by definition the code will never be exactly the same between the two networks.
In particular, the BitShares 0.9.2 release contains changes to code which is not executed in DevShares: https://github.com/BitShares/bitshares/compare/bts/0.9.1...bts/0.9.2
