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 ... 23
46
Currently the node is locat in East US. However, it can easily be migrated to a region most in need. May I receive your suggestion?

47
@sahkan Yes, I have added a TLS cert for: wss://api.vativ.io

Please reach out if you encounter any issues.

I appreciate your votes.

48
API server now live: wss://api.vativ.io  (ws://52.179.155.209)

As load demands, I will add node(s) to a load balancer and publish the endpoint.

49
I support your worker proposal. Thank you for all your contributions to date and upcoming.
-Fox

50
Ryan R. Fox - BTS Witness: fox

As an independent consultant I am often required to sign a NDA prior to entanglement with a client or a given project. Many remain in force at this time. None of which I feel create a conflict of interest in my role of validating transactions for the BitShares network.

Thank you for your continued support,
Ryan R. Fox

51
Thank you @pc for providing the CLI commands.

I was able to utilize these for testing FOXUSD (1.3.366) on the TESTNET. I am confident with the functionality of the code implemented therein.

Please note my APPROVAL of the code for release to MAINNET.

52
Technical Support / Re: genesis.json configuration
« on: August 22, 2017, 11:28:49 pm »
Please review the testnet documentation for Graphene:
https://docs.bitshares.org/testnet/private-testnet.html

53
General Discussion / Re: BitShares crowd at Consensus'17
« on: May 15, 2017, 05:58:31 pm »

54
General Discussion / Re: Automated Witness Deployment
« on: April 28, 2017, 09:09:23 pm »
I like the idea to wrap it in GUI. Can you provide more details there?

This template does not install any additional tools for price feeds. I have on for the TESTNET which installs python-BitShares. Recall, only elected witness may publish feeds, so not needed for a minimal node install.

55
General Discussion / Re: Automated Witness Deployment
« on: April 28, 2017, 05:45:04 pm »
Welcome back. Your skills are valued.

I have an Azure Template for BitShares on Ubuntu 16.04 LTS:

https://github.com/ryanRfox/azure-quickstart-templates/blob/master/bitshares-ubuntu-vm/README.md
https://github.com/ryanRfox/azure-quickstart-templates/blob/master/bitshares-ubuntu-vm/build_bitshares.sh

I am happy to connect regarding extending automation to other cloud providers.

Best,
Fox

56
Stakeholder Proposals / Re: [Witness Proposal] roelandp
« on: April 23, 2017, 06:19:28 pm »
Curious, WHY are there only 19 witnesses, did the committee vote to change that from 21 to 19?

From 24 to 21 to 19. Who or what is driving these changes?

The number of witness slots is the weighted average of the number of witnesses voted for by a given voter (proxy). Proxies voting for fewer witnesses will reduce the witness slots, which is what recently happened, resulting in two slots being eliminated. The number of witness slots is always an odd number and may not be less than 11. The committee has no impact on witness slots.

57
General Discussion / Re: why so many fork???
« on: April 14, 2017, 02:54:54 pm »
Respectfully, may I request you @alt to review your P2P logs to determine if the multiple blocks received contain distinct hashes? Is it possible your P2P node(s) are receiving the same block multiple times? I hope to isolate our troubleshooting to either the block generation side or the P2P transport/receipt side.

If you can identify blocks from a given witness with distinct block hashes, this would indicate generation issues, introducing a deliberate fork.

Best,
Fox

58
General Discussion / Re: why so many fork???
« on: April 14, 2017, 12:56:52 pm »
Can you elaborate on what you believe is going on? Are witnesses malfunctioning/misbehaving?

This is the witness node that generated the block(s) in question:
Code: [Select]
get_witness fox
{
  "id": "1.6.16",
  "witness_account": "1.2.167",
  "last_aslot": 15771235,
  "signing_key": "BTS5WsSbrh5tcF77d524MXHGkJoRgj2nSuK6KWfuM1hnv9VDgy7F5",
  "pay_vb": "1.13.32",
  "vote_id": "1:26",
  "total_votes": "72686675707190",
  "url": ".",
  "total_missed": 2892,
  "last_confirmed_block_num": 15672555
}
Code: [Select]
about
{
  "client_version": "2.0.161031-53-g4dc1001",
  "graphene_revision": "4dc1001a9b8be9bba9c1b45221371283cb9a750a",
  "graphene_revision_age": "21 weeks ago",
  "fc_revision": "31adee49d91275cc63aa3a47b3a9e3c826baccca",
  "fc_revision_age": "55 weeks ago",
  "compile_date": "compiled on Dec 29 2016 at 22:52:26",
  "boost_version": "1.58",
  "openssl_version": "OpenSSL 1.0.2g  1 Mar 2016",
  "build": "linux 64-bit"
}

Each of my other witness nodes contain distinct signing keys, therefore I can guarantee that only a single [witness_node] program is able to generate a block. My logs do not indicate generating multiple blocks as indicated by your P2P log.

I am keen to determine why this occurring.

59
Overall, I like your thoughts on how to use BOINC to generate more transactions against the TESTNET. Let's get the technical discussion going.

60
General Discussion / Re: how about to raise block reward?
« on: March 21, 2017, 01:41:41 am »
@alt I have reconfigured my script to publish accurately and timely once again. Respectfully requesting your support.
Best,
Fox

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