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

Pages: 1 ... 9 10 11 12 13 14 15 [16] 17 18 19 20 21 22 23
226
DevShares / Re: New DVS Delegate: Fox
« on: April 28, 2015, 04:45:52 am »
I've been running the 0.9.0 code on my Raspberry Pi 2 for a week now.  I'd like see how it handles the block production role, so looking for some votes. 

Thanks in advance!
-Fox

Code: [Select]
wallet (unlocked) >>> get_info
{
  "blockchain_head_block_num": 861616,
  "blockchain_head_block_age": "5 seconds old",
  "blockchain_head_block_timestamp": "2015-04-28T04:42:50",
  "blockchain_head_block_id": "e29db269164f7ed8f50345c4c2bc607d2b77e3fb",
  "blockchain_average_delegate_participation": "96.19 %",
  "blockchain_share_supply": "2,857,865,573.18902 DVS",
  "blockchain_blocks_left_in_round": 15,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2015-04-28T04:45:20",
  "blockchain_random_seed": "0d2dba2edd3ee8ccfe9cc8886672cd40ef2b8cfb",
  "client_data_dir": "/home/user/.DevShares",
  "client_version": "0.9.0-72-gb7937f2",
  "network_num_connections": 11,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-04-28T04:42:55",
  "ntp_time_error": 0.0023709999999999998,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "17 weeks in the future",
  "wallet_unlocked_until_timestamp": "2015-08-21T22:29:31",
  "wallet_last_scanned_block_timestamp": "2015-02-01T05:51:30",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

227
Please help me understand what impacts, if any, the BitAsset 3.0 proposal has on existing User Issued Assets. 
  • What is the relation between BitAsset Market Issued Assets, User Issued Assets and BitAsset 3.0?
  • What are the potential risks to existing User Issued Assets (issuers and holders) when BitAsset 3.0 enters the market?
 

228
General Discussion / Re: Privatizing BitAssets
« on: April 16, 2015, 12:23:10 pm »
If BitUSD were a privately owned asset then the manager of that asset (responsible for publishing the price feed) could make money directly proportional to adoption. 

I feel this experiment has been tried in the past, think eGold.  In my untrained opinion, the "manager" in the OP is an Issuer of a security and will be exposed to the full extent of the regulatory enforcement efforts of the pegged asset Issuer.   

The BitShares BitUSD is not issued by anyone; it is included as a feature of released P2P software.  The market for that pegged asset is between individuals with a protocol supporting their transactions. 

Overall I feel the OP introduces too many risks and does not enhance our collaborative community.

Respectfully,
Fox

229
We may be exhausted, but we're more excited about the prospects of BitShares than ever before!

Welcome home!  You two did great things for this community in those 24 days.

230
We need a roadmap and backlog! that everyone can contribute with ideas.

I follow this:
https://github.com/BitShares/bitshares/milestones

Been disappointed of late with slipping dates. Awaiting updates for 8.2 and 9.0 now past due. I endevour to make contributions as well.

231
DevShares / Re: DevShares 0.9.0 Feedback
« on: April 07, 2015, 08:38:19 am »
Use
Code: [Select]
git submodule update --init --recursive

Tried that, but got the same result:
Code: [Select]
Host:~/DevShares# git submodule update --init --recursive
fatal: reference is not a tree: 028f9409247be6d3d09a157e8eb347a173afc599
Unable to checkout '028f9409247be6d3d09a157e8eb347a173afc599' in submodule path 'libraries/leveldb'

I then tried to restart from the top with a fresh clone for the repository, but left out the "checkout dvs/0.9.0" line to remain on the master. Again, same result when attempting the "submodule update --init --recursive" line.

Next, I tried a new VPS host with the same results. Does my build script look incorrect?  What does the "reference is not a tree" bit mean? How to resolve?

232
DevShares / Re: DevShares 0.9.0 Feedback
« on: April 06, 2015, 10:58:45 pm »
First time with this issue: I am unable to build dvs/0.9.0.  I had no problem with previous dvs/ checkouts.  The submodule update is giving me an error I do not know how to correct:

Code: [Select]
host:~/DevShares$ git submodule update
fatal: reference is not a tree: 028f9409247be6d3d09a157e8eb347a173afc599
Unable to checkout '028f9409247be6d3d09a157e8eb347a173afc599' in submodule path 'libraries/leveldb'
host:~/DevShares$ git status
HEAD detached at dvs/0.9.0
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

        modified:   libraries/leveldb (new commits)

This is my build script:
Code: [Select]
# Build DEVShares
git clone https://github.com/BitShares/DevShares.git
cd DevShares
git checkout dvs/0.9.0
git submodule init
git submodule update
git status

As always, thanks for your assistance in advance.
-Fox

233
General Discussion / Re: How about a bitshares leadership summer meet
« on: March 22, 2015, 04:23:52 am »
Yes, I will attend a meetup in Las Vegas thru mid-July.

234
General Discussion / Re: [ANN] Cryptofresh is now open-source!
« on: February 03, 2015, 10:40:08 pm »
Model example of a 100% delegate providing more to the community.

235
DevShares / Re: Trouble Importing Keys to DVS Wallet
« on: February 02, 2015, 02:46:41 am »
No this command should work. Transactions will not show up during importing or scanning.

DVS was a 1:1 snapshot of BTS. If you already moved your genesis PTS stake in BTS before the DVS snapshot, then I wouldn't expect this import to give you any funds other than vesting balances.

Yes, of course!  I must export the BTS wallet for import into DVS.  Thanks for the clarifying reminder.

236
DevShares / New DVS Delegate: Fox
« on: February 01, 2015, 02:36:02 pm »
I have the latest client installed, synced and running stable for a couple of days.  Now, I ask for your support with votes.

Code: [Select]
wallet_approve_delegate fox
Code: [Select]
blockchain_get_account fox
Name: fox
Registered: Genesis (Keyhotee Founder)
Last Updated: 9 hours ago
Owner Key: DVS7Tb498vc8hCUqa8FnEhaztPPbUWysDsETZZjuAcLNs7Rch6MWc
Active Key History:
- DVS7Tb498vc8hCUqa8FnEhaztPPbUWysDsETZZjuAcLNs7Rch6MWc, last used 26 days ago

ID    NAME (* next in line)           APPROVAL       PRODUCED MISSED   RELIABILITY   PAY RATE PAY BALANCE         LAST BLOCK  VERSION
==========================================================================================================================================
169   fox                             0.00058710 %   0        0        N/A           100 %    0.00000 DVS         NONE        0.6.2

Block Signing Key: DVS7Tb498vc8hCUqa8FnEhaztPPbUWysDsETZZjuAcLNs7Rch6MWc
Public Data:
{
  "version": "0.6.2"
}

The client is ready to produce when enough votes are achieved:
Code: [Select]
getinfo
{
  "blockchain_head_block_num": 216581,
  "blockchain_average_delegate_participation": "100.00 %",
  "client_version": "0.6.2",
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

Looking forward to contributing thru testing.

237
DevShares / Re: Trouble Importing Keys to DVS Wallet
« on: February 01, 2015, 05:49:56 am »
I've just setup a clean DVS client 0.6.2 and followed my notes from way back (BTSX imports of a PTS wallet) using:
Code: [Select]
wallet_import_bitcoin PTS.datSupplying the correct password seems to do something, as it takes some time, then reports "Successfully imported <###> keys from PTS.dat" then proceeds to backup the wallet and begin scanning at block 1. 

In the past I recall seeing each transaction write to the screen during the import process, not here. The scan from block 1 seemed far too short. Forcing a wallet_rescan_blockchain did not turn up any transactions nor balances.

Is this command also a known bug?

238
General Discussion / Re: [URGENT] Delegates Please Upgrade to v0.4.26!
« on: December 12, 2014, 09:07:55 pm »
Now producing blocks with v0.4.26

239
General Discussion / Re: [URGENT] Delegates Please Revert Upgrade!
« on: December 12, 2014, 06:44:52 pm »
Currently building v0.4.26 @ 43%
Currently producing with v0.4.25-RC-2

240
A note regarding our work on the transition of PTS to a standalone DPOS chain:

PTS is alive and well and so is the social consensus. PTS will be the preferred sharedrop instrument of future 3rd party DACs. We have yet to decide whether to use the Nov. 5th snapshot (since a future snapshot may not be possible if mining stops completely), but rest assured that we have a functional testnet, new website and marketing in the works, and an active group of dedicated developers and marketers.

Stay tuned for more information...

@alphBar
How does the "Invictus Innovations to Return PTS Donations" announcement [1] , thereby diluting the existing PTS chain, play into your consideration for use of the 5 November snapshot?  How is the social consensus for PTS(DPOS) impacted by their announcement?

Regards,
Fox

[1] https://bitsharestalk.org/index.php?topic=11289.75

Pages: 1 ... 9 10 11 12 13 14 15 [16] 17 18 19 20 21 22 23