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 2 3 4 [5] 6 7 8 9 10 11 12 ... 23
61
Thanks for organizing the pre-party on Tuesday Chris4210. I'll drop in from time-to-time, but cannot commit to both days full time.

Thom, let me attempt to answer most of your question to the best of my knowledge. Others, please correct my ignorance. The test Wednesday is to achieve the maximum sustained transactions per second across a distributed and decentralized network of at least 11 witness nodes. Many times that number of transaction generating nodes (cli_wallet) will be required to flood the network with operations from around the globe. This is where we need the most help.

The $200 Azure credit does come with the requirement of a credit card number and a non-VOIP phone number. Some level of identity to mitigate against continually using their offering without payment. Upgrade to Pay-as-you-go to get additional cores for your subscription. Cancel at any time before your credit is exhausted and/or 30 days = 'free'.

Anyone can use this build script on any Ubuntu 16.04 LTS server (AWS, Digital Ocean, etc.). Nothing is Azure specific herein:
Code: [Select]
https://github.com/ryanRfox/BitSharesTESTNET/blob/master/build_BitSharesTESTNET.sh
You will not need to import any balance for this testnet. Any BTS you hold are not applicable to this chain, as the genesis did not include any of those balances. Xeroc will transfer you a sufficient amount of TEST tokens for the test. Just send him a note when your account is registered. You may also ping me or GChicken for a started lot. That should cover the time zones.

As I have not yet hooked up a faucet to my Azure script, you should register a new account through the web wallet Xeroc setup for the testnet:
Code: [Select]
https://testnet.bitshares.eu
You will need to export the keys from that web wallet to import to your cli_wallet. The import can be found in step 12 of the README file:
Code: [Select]
https://github.com/ryanRfox/BitSharesTESTNET/blob/master/README.md
Sorry, I cannot answer the questions about Vagrant nor Docker.

Look forward to having you help crush this network!


62
General Discussion / Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« on: March 13, 2017, 12:08:39 am »
but I still have a few questions to this list from point 12 ii and above
https://github.com/ryanRfox/BitSharesTESTNET

Quote
Use the WIF private key you copied earlier from the ~/brain_key.json file unlocked >>> import_key 5yourPrivateKeyStartsWith5...

>>> import_key accoutname 5KgFzmuA8FXMgFzmuA8FgFzmuA8FgFzmuA8F true
point 14
but I don't have any file here :

tail: cannot open ~/testnet/cli_wallet/wallet.json for reading: No such file or directory

Sorry all, I had poor syntax in my README file. There are three (3) parameters for import_key
Code: [Select]
import_key <account_name> <WIF_private_key> <bool>There for it should look something like:
Code: [Select]
unlocked >>> import_key fox 5ALLprivateKeysStartsWith5andAbunchOfChars true
Also, I neglected to create the /home/$USER_NAME/testnet/cli_wallet folder prior to launching the cli_wallet, so it was unable to save the wallet file. I have now added that to the script so it 'should' function properly. Also, I added the web socket RPC flag to the wallet startup. The relevant code changes are here:
Code: [Select]
##################################################################################################
# Create a script to launch the cli_wallet using a wallet file stored at                         #
# /home/$USER_NAME/$PROJECT/cli_wallet/wallet.json                                               #
##################################################################################################
mkdir /home/$USER_NAME/$PROJECT/cli_wallet/
cat >/home/$USER_NAME/launch-$PROJECT-wallet.sh <<EOL
/usr/bin/$CLI_WALLET -w /home/$USER_NAME/$PROJECT/cli_wallet/wallet.json \
                     -s ws://$LOCAL_IP:$RPC_PORT \
-H 127.0.0.1:$WALLET_HTTP_RPC_PORT \
-r 127.0.0.1:$WALLET_WS_RPC_PORT
EOL
chmod +x /home/$USER_NAME/launch-$PROJECT-wallet.sh

63
Stakeholder Proposals / Re: Witnesses - please report in
« on: February 25, 2017, 06:50:13 pm »
witness node with feeds
backup witness nodes (geographically dispersed)
testnet node
Azure blockchain as a service
Public speaking

64
Stakeholder Proposals / Re: [worker] Python-steem and uptick (1.14.52)
« on: February 03, 2017, 06:38:19 pm »
This worker proposal will provide value to the BitShares network. I support this effort.

65
Meta / Re: Are forum email notifications working?
« on: January 13, 2017, 02:04:56 am »
I sent you a test message. Did it notify your inbox?

66
Meta / Re: Subforum consolidation
« on: January 07, 2017, 04:00:29 am »
Making the proposed changes seems a good start. @vikram do you have the required forum access to execute the updates? If not you, then with whom do we connect to initiate this?

67
Yes, you may check the balance for your account using an online block explorer. I like CryptonFresh by @roadscape

Just modify the URL below to replace "fox" with "youraccountname"

http://cryptofresh.com/u/fox

All balances are public.

68
The web wallet is stored within the web browser. Clearing the cache will remove the wallet. The UI provides the option to create a backup file that you may store elsewhere. Thereafter this wallet file may be restored or imported into any browser. You will need to provide the password to open the wallet within the browser.

69
General Discussion / Re: Bit20 - The cryptocurrency index fund
« on: December 29, 2016, 05:38:11 am »
Publisher @Fox set MSSR=150%,others 110%,why?
Sorry @天籁 my pricefeed parameter was incorrect and has now been updated to 110% as requested by @EstefanTT. Thank you for noting my oversight.

Point of information: The Graphene default for "maximum_short_squeeze_ratio" is %1500 (150%), so I needed to explicitly supply the requested value within my transaction construction.

70
General Discussion / Re: who can tell me what's the GOLD price?
« on: December 28, 2016, 09:02:19 pm »
I have adapted the @xeroc developed pricefeed script included within the python-graphenelib repository:
Code: [Select]
https://github.com/xeroc/python-graphenelib
If you are using this script, you may use the steps below as a guide to provide valid feeds for gold and silver.

1.   Edit config.py to remove Yahoo as a feed provider for GOLD and SILVER (Yahoo is not providing a valid USD price at this time)
1.1         Locate the feedsources.Yahoo function
1.2         Comment out the XAU and XAG entries using the hash symbol
Code: [Select]
#"XAU"       : "GOLD",
#"XAG"       : "SILVER",

2.   Ensure Quandl is enable as a feed provider for GOLD and SILVER
Code: [Select]
feedSources["quandl"]    = feedsources.Quandl(datasets={  # You provide a valid API Key or this will fail!
                                                  "GOLD:USD": [
                                                      "WGC/GOLD_DAILY_USD",
                                                      "LBMA/GOLD",
                                                      "PERTH/GOLD_USD_D"
                                                      ],
                                                  "SILVER:USD": [
                                                      "LBMA/SILVER",
                                                      "PERTH/SLVR_USD_D"
                                                      ]
                                                  }
                                              )

3.   Acquire a Quandl API Key
3.1         http://help.quandl.com/article/118-how-do-i-pass-along-my-user-id-or-api-key
3.2         It’s free, but requires a valid email account, GitHub account or other authentication provider

4.   Edit config.py to add your Quandl API Key
Code: [Select]
quandlApiKey = "dsahFHUiewjjd" # This is an invalid API Key. Replace with yours!
5.   Edit feedsources.py to include your Quandl API Key
5.1         Locate the Quandl URL string:
Code: [Select]
url = "https://www.quandl.com/api/v3/datasets/{dataset}.json?start_date={date}.format(5.2         Modify the query string portion of the URL to include your API Key from the config.py file
Code: [Select]
url = "https://www.quandl.com/api/v3/datasets/{dataset}.json?start_date={date}&api_key=" + config.quandlApiKey.format(
These modifications should allow your witness to provide a valid feed for both gold and silver.

I know others are using the scripts from the @wackou provided bts_tools repository:
Code: [Select]
https://github.com/wackou/bts_tools
I quickly glanced at this codebase, but did not locate Quandl as a feed provider.    I will endeavor to scratch together some code for bts_tools as well.

Cheers!
Fox


71
General Discussion / Re: Transaction Throughput Testing
« on: December 27, 2016, 07:45:51 pm »
I will contribute at least one node to the TESTNET for this effort. Please provide a link to the github repository with your transaction generation script(s). As referenced above, previous test have been limited  not by the witness nodes processing the transactions, rather the ability of the clients to sent transactions quickly enough and at scale to generate a high volume. Focus your effort on building the transaction construction and broadcasting.

72
General Discussion / Re: BitShares administrative and maintenance tasks
« on: November 01, 2016, 03:11:20 am »
Vikram,
Warmest welcome back! Congratulations on forming a company in this space. Your prior contributions speak volumes for what it accomplish in the future. Will surely support your efforts toward a worker proposal.

Cheers!
Fox

73
General Discussion / Re: btsbots wallet release v0.0.1
« on: October 29, 2016, 02:53:37 am »
Welcome back Alt. Appreciate the efforts here and will now give it a go.

Cheers!

74
Is Bunkerchain Labs Inc willing to confirm the licensing arrangement with Cryptonomex Inc for the Graphene technology used in Peerplays?

Has Bunkerchain Labs Inc retained the license grant prior to the ICO, or do they anticipate gaining the license grant in the future?

Will any amount of ICO funds raised offset Graphene licensing fees?

75
General Discussion / Re: Request - Wallet API Access Using curl
« on: May 07, 2016, 03:34:49 am »
RESOLVED:
Code: [Select]
curl --data '{"jsonrpc": "2.0", "method": "call", "params": [0,"suggest_brain_key",[]], "id": 2}' http://127.0.0.1:8092/rpc

Not much different there. Just note the port it now connects to 8092 (cli_wallet) vs. 8090 (witness_node) prior. A simple, obvious error on my part.

Thanks both @abit and @xeroc for the pointers.

Pages: 1 2 3 4 [5] 6 7 8 9 10 11 12 ... 23