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 - santaclause102

Pages: 1 ... 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 ... 166
376
I've found running BitShares GUI on windows completely intolerable.  I gave up on that a long time ago.  Its only stable on Linux and mac it seems.   

So true.  I've been having very similar problems to Adam's the past couple days.  Keeps crashing 50-75% of the way through.  Been trying to get it to finish syncing the blockchain so I can buy some more NOTES! ;)
If you use this http://wiki.bitshares.org/index.php/BitShares/Chain-Server it can crash and you can resume downloading. Normally if it crashes then you have to begin from 0...

377
I am just trying to sync as well. This looks promising atm https://bitsharestalk.org/index.php/topic,17629.msg224847.html#msg224847 (downloading the chain from a chain server instead of via the p2p network)

378
Technical Support / Re: Syncing issues
« on: July 20, 2015, 01:47:27 pm »
Thanks a lot xeroc!

So what I did in the end that made it work: Because the config.json file didn't exist I created a new one like xeroc said. That though didn't let me start the client anymore (error msg). Then I deleted the config.json file again and restarted the client and that created a config.json file by itself  :o

I then followed the instructions here: http://wiki.bitshares.org/index.php/BitShares/Chain-Server

379
Technical Support / Re: Syncing issues
« on: July 20, 2015, 12:53:35 pm »
There is no config.json file in my .BitShares folder though, only a node_config.json file which contains: listen_endpoint..., accept_incomming_connections:...., wait_if_endpoint:..., private key:....

This is odd .. Ok.. let's try this:
1) open your client or gui
2) go to the console
3) type "info"
4) the directory that stores the config file is given as "client_data_dir"
5) in that dir. there has to be a config.json file
hmmm client_data_dir says: "home/.../.BitShares" but there are still only these two json files in the .BitShares folder.

380
Technical Support / Re: Syncing issues
« on: July 20, 2015, 12:42:36 pm »
So in case the chain server I connect to is lying it would be apparent that it did lie as soon as I start connecting to the p2p network myself?
Yup .. I am not even sure the chain server CAN lie at all .. because active delegates have to sign each block that the chain servers are broadcasting to you .. to fake a block he needed the delegates signing key!
Ok. Great.

There is no config.json file in my .BitShares folder though, only a node_config.json file which contains: listen_endpoint..., accept_incomming_connections:...., wait_if_endpoint:..., private key:....
That is all that is in there.
Then there is also a checkpoints.json file with a bunch of strings in it.


381
Technical Support / Re: Syncing issues
« on: July 19, 2015, 06:09:26 pm »
Sounds interesting. Thanks for the hint. Is it possible download the chain from more than one chainserver so that it is effectively a 2 out of 2 or 3 out of 3 or so trust model?
I am afraid it's not :(

Quote
It should require less trust anyway because I do not download a file someone created but information tat has been standardized by the protocol. Agreed?
Yup. Blocks are still validated. Just the download process is faster
So in case the chain server I connect to is lying it would be apparent that it did lie as soon as I start connecting to the p2p network myself?

382
Technical Support / Re: Syncing issues
« on: July 19, 2015, 04:49:41 pm »
There are also chain server from which you can sync:
http://wiki.bitshares.org/index.php/BitShares/Chain-Server
Sounds interesting. Thanks for the hint. Is it possible download the chain from more than one chainserver so that it is effectively a 2 out of 2 or 3 out of 3 or so trust model?

It should require less trust anyway because I do not download a file someone created but information tat has been standardized by the protocol. Agreed?

383
Technical Support / Re: Syncing issues
« on: July 19, 2015, 04:40:49 pm »
Thanks Fox,

I forget that it was possible to use get_info in the client.... I have version 0.9.2 which should be the latest version.

Get info also tells me:
Blockchain_head_block_age: 51 weeks.
blockchain_head_block_time: ...

When I do get_info again after a few minutes the blockchain_head_block_time is still exactly the same. So it means it doesn't actually sync. Why? What can I do about it?

If there is someone I would trust for externally downloading the blockchain than it would be fav! But I would prefer to not do that at all... Thanks though for the hint. I wouldn't have thought about it...

384
Technical Support / Syncing issues
« on: July 19, 2015, 10:19:42 am »
I have compiled the latest Linux client version (0.9.2). I said should because I downloaded it 1 month ago and there was no new release here since then: https://github.com/BitShares/bitshares/releases. Is there a formal way to check what version I have?

The issue: I synced and got stuck at 33% yesterday. I have let it sync for the whole night and still was at 33% this morning.
After having deleated the .bitshares folder I started syncing again and I am now stuck at 3% since a few hours.

It says: Severe network problems. Last block synced 355 days and .. hours and ... seconds ago. And that amount of time is growing.

Any ideas?

385
What other than worker proposals which are anyway part of 2.0 would "Follow My Vote tools" allow to vote for?
I think he is talking about the possibilities to vote on-chain in general. Those would also include, witnesses, delegates, and most (when not all) fees of the system ..
^
That is all part of 2.0. I couldnt come up with something BTS stakeholders could vote on other than what you mentioned.

386
In its infancy, this network and the community surrounding it has been highly dependent on a few key actors for leadership, growth, and survival.  This is normal and healthy for a developing network, but it would be terribly unhealthy to stagnate in this stage.  I am quite grateful for the dedication, innovation, and vision that has been poured into BitShares by its founders and other early leaders.  I hope they will remain active members and contributors to this community, but with the impending transition to graphene, the time has come to mature our social structure into a more fault tolerant mesh that reflects the elegant design of our network.

To achieve this, I propose the following prioritization strategy:

1. Complete BitShares 2.0 migration
2. Create user friendly Follow My Vote tools to enable stake voting on later proposals
?. Privacy features
?. Bond market
?. Decentralized BitShares ID based communication and social platform to replace centralized forums
?...

As soon as step one is complete, the community can commence a massively parallel marketing campaign using the referral system.  As soon as step two is complete, all remaining development goals can be proposed and sequenced through stakeholder voting.  Developers ideally should maintain multiple links to the community for fault tolerance, rather than relying so much on bytemaster to speak for them.  We need to outgrow dependence on any single individual as a decision making bottleneck.  In the future, good ideas should propagate through our social mesh virally, snowballing stake support as they go.  Where they originate is irrelevant.

This is the last major strategy and vision decision that needs to be pushed through with the current leadership structure.  This will enable them to work themselves out of a job and become just a few more highly respected community members and stakeholders.  With BitShares 2.0 + an FMV stake voting system, I believe this network can begin to grow even beyond the intentions of its founders.

Please state if you agree that using 2.0 and FMV to end BitShares remaining reliance on centralized leadership should be our top priority.  If you disagree, please state your reasoning.  The goal is in sight, but we need all need to be together on this, especially the dev team.
What other than worker proposals which are anyway part of 2.0 would "Follow My Vote tools" allow to vote for?

387
General Discussion / Re: Status Update
« on: July 11, 2015, 09:13:28 am »
What would the memory usage roughly have been if the squatter didn't register his names?

388
General Discussion / Technical trading: Time frames
« on: July 06, 2015, 05:18:11 pm »
The bigger / smaller the volume you are trading compared to the daily trading volume the more / less will you move the market. A big volume trader will therefore not be able to profit from small short term swings. A small volume trader can trade all paterns / time frames. I hope that makes sense?

I know a few things about technical trading but not too much... I asked myself whether there is a formula or a rule of thumb that tells you what time frames the patterns should have that you are trading depending on the ratio of your trading volume compared to the daily trading volume of the respective asset. Is anyone are of something like that?

390
General Discussion / Re: Announcing Brownie Points (BROWNIE.PTS)
« on: July 03, 2015, 05:50:09 pm »
Initially I asked lots of questions, not sure how that counts :)

- I fought endless explanation battles on btt, disqus, nxt forum and reddit about bitshares and dpos. The best ones: Reggie battle (in the comments section, user BtoC),  NXT Forum
- I contributed to the wiki (not nearly as much as others though, xeroc for example or gamey).
- I wrote two articles for the Bitshares blog that are currently not online anymore: The value proposition of BitShares I & II.
- I hope that I gave constructive critique.
- I helped newcomers who tried to understand Bitshares get up to speed - I remember Thom, Karnal and Kencode (all valuable community members now).
- I translated one of the many Bitshares.org sites to German (the one Brian Page made...).

I would be honored by some points but I feel I already got much: Most of all I am super thankful for the patience Bytemaster had (I learned a lot!) and the openminded, friendly and principle based attitude of this community.

BTS handle: delulo

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