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

Pages: [1] 2 3 4
1
Thanks for your votes so far.

Please submit your mainnet API node to https://github.com/bitshares/bitshares-ui/ .

My nodes will be available in the next UI release (see PR). You can already find them in the staging wallet.
Any feedback on the latency is welcome.

My testnet witness (witness.zapata) and API node (wss://testnet.dex.trading) have been updated (see release thread).
I missed one block in the deployment process as I switched my signing key back to my main witness node while it was my turn.
I will take care to avoid this case in the future.
(Note that I had a typo in my previous post, you should have read 597, instead of 579. I'm now at 598).

This week I also added Bitshares integration to EOSIO/demux-js. You can find out more information on Demux here.

2
General Discussion / Re: BitShares TESTNET Feature Release 2.0.20180803
« on: August 05, 2018, 02:04:42 pm »
My testnet witness (witness.zapata) and API node (wss://testnet.dex.trading) have been updated.

enable-standby-votes-tracking (see #987) has been added to the configurations and configured as recommended (false for witness, true for api).

Docker image (bitshares/bitshares-core:testnet) is working correctly and gracefull shutdown fix (#1077 #1115) have been succesfully tested.

3
Can you please provide a block producer for the testnet as well?
To get my votes, I usually look how well they perform on the testnet (block production only, no price feeds).

My testnet block producer is running since early may and active since 12/05/2018. The account is: witness-zapata.

I also consider that running a testnet block producer is a mandatory task for a witness. I always test my changes on testnet before applying them on mainnet. It was also required for some developments. I am trying to keep it as stable as the main one.

On testnet, I missed 579 blocks so far:
  • the first ~540 was because initially I didn't put the correct private/public key pair, and didn't notice that I was activated. To prevent the issue on mainnet I monitor the activation (see this commit)
  • then I missed ~20 to update the version and at that time I was not running a backup node;
  • 1 block missed for a non investigated issue (short network loss);
  • then I missed ~15 block during my chaos testing to validate the backup procedures: I switch signing key after 3 blocks, and I tested muliple cases.
Note that I have heavely updated the underlying servers and kubernetes cluster while running the witness without issues.

4
Stakeholder Proposals / [Witness Proposal] 1.6.129 - zapata42-witness
« on: July 30, 2018, 08:21:09 pm »
Hello,

dear Bitshares community, I want to propose my services as a Bitshares Witness.

Please vote for zapata42-witness.

Who am I?

I am a developer with 13 years of experience in finance sector, based in Paris (France). I have worked for BNP Paribas Corporate Investment Banking in the equity derivatives business for the past 10 years in projects as varied as price publication, position keeping or request for quotes, and as a developer, technical lead or architect. Java is my main programming language but I have good knowledge of Python, Javascript, and Ruby. See below for my full resume.

I came to know Bitshares about one year ago, and since then I closely followed it as I was impressed by the technology, the balanced economical model and the distributed governance. I started to contribute on my spare time as I could:

Now I want to be more involved in Bitshares, and as I am not a C++ nor a React programmer (yet?), I feel like witness role currently suit me best to help the community. You will found below my current setup, and what I plan to do once voted in.


My current setup:

    Hardware: 3 x VPS 4 cores CPU at 2.4ghz, 24GB RAM, 100GB SSD hard drive, 250Mpbs internet bandwith, Location: France.
    (I consider this a minimum, see below for my target plan)
   
    I run 2 witness mainnet nodes (account zapata42-witness) and 2 witness testnet node (witness-zapata).
    They are monitored through an improved version of @clockwork's telegram monitoring bot that handle automatic key switch and price feed monitoring.

    The price feed is ready, I already publish @nasdaq assets (see AMAZONCOM) and I use a stabilized version of @xeroc's pricefeed.

    Additionnaly I host some services:
        Mainnet API:         https://api.dex.trading  (max-ops-per-account = 100)
        Mainnet Seed:       seed.dex.trading:2001
        Testnet API:          https://testnet.dex.trading
        Wallet:                  https://wallet.dex.trading or https://bitshares.dex.trading (patched version that use my referral link as default)

    Services are served through multiple proxies (currently NGINX) that do rate limiting and SSL termination.
    For SSL certificate is issued by Let's encrypt and renewal is automated.
    Everything run on a private multi datacenter Kubernetes cluster (so fully Dockerized and resilient) and monitored through Prometheus/Grafana.
    The setup is automated and ready to scale, see my plan below.

My plan:

If I get voted as an active witness my focus will be on:
  • Providing a stable block producer
  • Providing a stable, accurate and auditable price feed of most Market Pegged Assets
  • Grow Bitshares infrastructure, community and software ecosystem
This means:
  • Upgrade the infrastructure. With the current witness pay (~30 witness / bts=0.2$ / 1bts per block) I aim to add:
                        6 x Dedicated 4c/8t 3Ghz CPU, 64go RAM, 1To SSD hard drive, 250Mpbs internet bandwith, Locations: france, germany, uk, canada, singapore, australia
  • Continuous improvements of the setup like: geo optimizations for latency (GeoDNS + regional vlan), premium wildcard SSL certificate, premium api acess, ...
  • Additional to classic API nodes, I will install and serve community tools like: Open-Explorer, Python API Backend, Elastic Search database with a data visualization tool like Kibana/Graphana, Bitshares HUG, and any future interesting project of the community;
  • Active participation (code contributions, code/issue/bsip review, testing) to community initiatives (core, ui, tools, documentation) as a developer;
  • Participate to meetups and hackathons to promote Bitshares;
  • Regularly run third party professional penetration testing on the setup;
  • if BTS price allow me to do it, hire other people to help me.

So why voting for zapata42-witness ?
  • Experienced software developer with professional experience in developing and running financial highly critical software;
  • Professional experience in price contribution in a main financial company;
  • Proven will and capacity to contribute on Bitshares related projects;
  • Full setup (witness, pricefeed + api) in place, and wide range of services in target;
  • Active investment in Bitshares ecosystem (infrastructure & time) planned;
  • Knowledgeable in blockchain internals;
  • Relations in French fintech and financial institutions;
  • Fresh blood.


Contact:
  Telegram: @Zapata_42
  LinkedIn profile

5
General Discussion / Re: Shares of Nasdaq&NYSE at Bitshares
« on: June 12, 2018, 10:25:41 pm »
Note tat I have created AMAZONCOM on testnet also, if others witness wants to contribute ('ALLOW WITNESSES TO PROVIDE FEEDS' has been enabled).

6
account zapata42-witness is added to the whitelist for publication of feeds by smart asset AMAZONCOM
As soon as you manage to publish the feeds for smart asset AMAZONCOM, I will add you to the white list of all smart assets
Please try...

I have the price of the stock in dollars and multiply it by the exchange rate bts/usd.
I take the course of bts from the purse of the bitshares. Those. from a usd / bts pair on the bitshares exchange.


I have started the publication for AMAZONCOM.

Sorry for the delay I found another issue in bitshares-pricefeed.

I think the spread is due to the different USD:BTS price we use.
I use the current bitUSD DEX feed (= bitUSD settlement price), you seems to use the DEX BTS/bitUSD orderbook. Currently there is a big spread between the two.
I feel like the bitUSD current feed it's more appropriate.
Your opinion is welcome.

7
I have updated xeroc's bitshares-pricefeed to be able to publish your assets (see this issue).

It currently support IEX, AlphaVantage, RobinHood and Google Finance as stock price sources.

When I try to publish using IEX for Stock/USD price and Bitshares DEX current feed for USD/BTS, I have a spread with your prices (see column blockchain):
Code: [Select]
6/10/2018 3:03:32 PM+--------------+------------+--------------+--------------+---------------------+---------------------+---------------------+--------------+----------------------+--------+--------+-------------------------+-------------+
6/10/2018 3:03:32 PM|    symbol    | collateral |  new price   |     cer      |         mean        |        median       |      wgt. avg.      | wgt. std (#) |      blockchain      |  mssr  |  mcr   |      my last price      | last update |
6/10/2018 3:03:32 PM+--------------+------------+--------------+--------------+---------------------+---------------------+---------------------+--------------+----------------------+--------+--------+-------------------------+-------------+
6/10/2018 3:03:32 PM|   FORDCOM    |    BTS     | 0.0158990901 | 0.0166940447 | 0.0158990901 (0.00) | 0.0158990901 (0.00) | 0.0158990901 (0.00) |  0.00 ( 1)   | 0.0169090580 (-5.97) | 110.0% | 175.0% | -1.0000000000 (-101.59) | unknown ago |
6/10/2018 3:03:32 PM|   VISACOM    |    BTS     | 0.0014277794 | 0.0014991683 | 0.0014277794 (0.00) | 0.0014277794 (0.00) | 0.0014277794 (0.00) |  0.00 ( 1)   | 0.0015184220 (-5.97) | 110.0% | 175.0% | -1.0000000000 (-100.14) | unknown ago |
6/10/2018 3:03:32 PM| FACEBOOKCOM  |    BTS     | 0.0010173400 | 0.0010682070 | 0.0010173400 (0.00) | 0.0010173400 (0.00) | 0.0010173400 (0.00) |  0.00 ( 1)   | 0.0010817246 (-5.95) | 110.0% | 175.0% | -1.0000000000 (-100.10) | unknown ago |
6/10/2018 3:03:32 PM|  BOEINGCOM   |    BTS     | 0.0005206468 | 0.0005466791 | 0.0005206468 (0.00) | 0.0005206468 (0.00) | 0.0005206468 (0.00) |  0.00 ( 1)   | 0.0005539305 (-6.01) | 110.0% | 175.0% | -1.0000000000 (-100.05) | unknown ago |
6/10/2018 3:03:32 PM|   APPLECOM   |    BTS     | 0.0010035419 | 0.0010537190 | 0.0010035419 (0.00) | 0.0010035419 (0.00) | 0.0010035419 (0.00) |  0.00 ( 1)   | 0.0010670597 (-5.95) | 110.0% | 175.0% | -1.0000000000 (-100.10) | unknown ago |
6/10/2018 3:03:32 PM|   EBAYCOM    |    BTS     | 0.0047748571 | 0.0050135999 | 0.0047748571 (0.00) | 0.0047748571 (0.00) | 0.0047748571 (0.00) |  0.00 ( 1)   | 0.0050776123 (-5.96) | 110.0% | 175.0% | -1.0000000000 (-100.48) | unknown ago |
6/10/2018 3:03:32 PM|  ALIBABACOM  |    BTS     | 0.0009381138 | 0.0009850195 | 0.0009381138 (0.00) | 0.0009381138 (0.00) | 0.0009381138 (0.00) |  0.00 ( 1)   | 0.0008983187 (4.43)  | 110.0% | 175.0% | -1.0000000000 (-100.09) | unknown ago |
6/10/2018 3:03:32 PM|   TESLACOM   |    BTS     | 0.0006056129 | 0.0006358935 | 0.0006056129 (0.00) | 0.0006056129 (0.00) | 0.0006056129 (0.00) |  0.00 ( 1)   | 0.0006353301 (-4.68) | 110.0% | 175.0% | -1.0000000000 (-100.06) | unknown ago |
6/10/2018 3:03:32 PM|  AMAZONCOM   |    BTS     | 0.0001142400 | 0.0001199520 | 0.0001142400 (0.00) | 0.0001142400 (0.00) | 0.0001142400 (0.00) |  0.00 ( 1)   | 0.0001214706 (-5.95) | 110.0% | 175.0% | -1.0000000000 (-100.01) | unknown ago |
6/10/2018 3:03:32 PM| MCDONALDSCOM |    BTS     | 0.0011389438 | 0.0011958909 | 0.0011389438 (0.00) | 0.0011389438 (0.00) | 0.0011389438 (0.00) |  0.00 ( 1)   | 0.0011912059 (-4.39) | 110.0% | 175.0% | -1.0000000000 (-100.11) | unknown ago |
6/10/2018 3:03:32 PM|  NETFLIXCOM  |    BTS     | 0.0005335413 | 0.0005602184 | 0.0005335413 (0.00) | 0.0005335413 (0.00) | 0.0005335413 (0.00) |  0.00 ( 1)   | 0.0005088366 (4.86)  | 110.0% | 175.0% | -1.0000000000 (-100.05) | unknown ago |
6/10/2018 3:03:32 PM|   BAIDUCOM   |    BTS     | 0.0007298418 | 0.0007663339 | 0.0007298418 (0.00) | 0.0007298418 (0.00) | 0.0007298418 (0.00) |  0.00 ( 1)   | 0.0007762339 (-5.98) | 110.0% | 175.0% | -1.0000000000 (-100.07) | unknown ago |
6/10/2018 3:03:32 PM| MICROSOFTCOM |    BTS     | 0.0018929351 | 0.0019875818 | 0.0018929351 (0.00) | 0.0018929351 (0.00) | 0.0018929351 (0.00) |  0.00 ( 1)   | 0.0020129587 (-5.96) | 110.0% | 175.0% | -1.0000000000 (-100.19) | unknown ago |
6/10/2018 3:03:32 PM| STARBUCKSCOM |    BTS     | 0.0033989221 | 0.0035688682 | 0.0033989221 (0.00) | 0.0033989221 (0.00) | 0.0033989221 (0.00) |  0.00 ( 1)   | 0.0036148342 (-5.97) | 110.0% | 175.0% | -1.0000000000 (-100.34) | unknown ago |
6/10/2018 3:03:32 PM|   CISCOCOM   |    BTS     | 0.0044245398 | 0.0046457668 | 0.0044245398 (0.00) | 0.0044245398 (0.00) | 0.0044245398 (0.00) |  0.00 ( 1)   | 0.0047064385 (-5.99) | 110.0% | 175.0% | -1.0000000000 (-100.44) | unknown ago |
6/10/2018 3:03:32 PM+--------------+------------+--------------+--------------+---------------------+---------------------+---------------------+--------------+----------------------+--------+--------+-------------------------+-------------+

Any idea why there is such a spread? As JohnR asked, could you give us some insights on your pricing mechanism?

I can setup a price feed if you white-list zapata42-witness.

The code is under MIT license so any one can use it to setup their feed, I hope this will help decentralization.

8
Updated a few days ago, ready for the fork.
Sorry if I misses some blocks, I tested a (sucessfull) update from my phone, and I dont run multiple instances.
Thanks. Are you a mainnet witness? If yes, what's your witness name / ID?

I'm not (yet?) candidate on the mainnet.

9
Updated a few days ago, ready for the fork.
Sorry if I misses some blocks, I tested a (sucessfull) update from my phone, and I dont run multiple instances.

10
General Discussion / Re: Binance Dexathon - Discussion
« on: May 23, 2018, 09:09:01 am »
Any news?

For your information, the CEO talk about his expectations on this week epicenter.tv podcast: https://epicenter.tv/episode/235/

It seems they want to build something really similar to Bitshares (DAC included).
For them performances and liquidity are the highest priority.
They also say they will promote DEX in general, and try to bring liquidity.

11
Technical Support / Re: Change Registrar for referral accounts
« on: May 15, 2018, 08:00:49 pm »
Ok and how can I do this?
Something like this: http://docs.bitshares.org/testnet/7-faucet.html

I'm not sure if it's what you want.. need to run a server, and best if you host a web wallet for other users.

Note that bitshares.eu also propose a "refered" faucet service, see: https://bitshares.eu/referral/

Then you need to fork the UI code and patch the faucet URL, see this example.

That's what I did for: https://wallet.dex.trading


12
By the way, anyone who want to be voted please leave a message.

My test witness "witness.zapata"  has been upgraded sucessfully to "test-2.0.180510" using Docker image.
I run also a test API node with the same version: testnet.dex.trading

Can you vote me in?

13
Technical Support / Re: ETF on BitShares
« on: April 12, 2018, 01:48:52 pm »
Furthermore, i have looked to some MPA  on bitshares and there is also a settlement price. What does the settlement price exactly mean and how is it calculated?

To publish a feed you have to provide:
    - settlement_price: the rate ETF / USD (or EUR or BTS or whatever base asset you use)
    - core_exchange_rate: the exchange rate to pays DEX fees using your asset (see fee pool mecanism)
    - maximum_short_squeeze_ratio: collateral ratio that triggers a force settlement
    - maintenance_collateral_ratio: minimum Collateral ratio required to borrow a share of the ETF

I would recommand you to read all the documentation on the topic:
   - http://docs.bitshares.org/bitshares/user/dex-short.html
   - http://docs.bitshares.org/bitshares/user/dex-margin-mechanics.html

14
Technical Support / Re: ETF on BitShares
« on: April 12, 2018, 01:09:34 pm »
What are your thoughts about the permission: disable force settling?

You should allow force settling, this will give the opportunity to an ETF share owner to exit and get the colllateral even if there is no sellers.
If there high liquidity and market makers, force settling should not be usefull, but better to keep it as a safety net.

15
General Discussion / Re: Smart-asset devaluation
« on: April 10, 2018, 02:42:02 pm »
Usually you have multiple price feed publishers, the blockchain will use the median price.
It's better to trust the feed publishers, and have many of them with different implementations.

Pages: [1] 2 3 4