Main Menu
Menu

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.

Show posts Menu

Messages - ElMato

#1
Witness: elmato
matias[dot]romeo[at]diventi.com.ar
#2
Quote from: xeroc on April 04, 2018, 08:08:30 AM
Quote from: ElMato on April 04, 2018, 07:57:37 AM
elmato API Nodes

wss://api.btsxchng.com

Architecture:


  • 3 Zones

    • Asia Pacific (Singapore)
    • US East (N. Virginia)
    • EU (London)
  • 3 Load balancers (one per zone)
  • 9 API nodes (3 per load balancer)
  • Traffic policies on geolocation (Asia/North America/Europe/Other)


PR
https://github.com/bitshares/bitshares-ui/pull/1399
@Elmato: How did you manage to make websocket connection work with geo-location? To my knowledge websocket doesn't support redirects :-(

@xeroc: as @clockwork mentioned, it DNS level.
This is, depending on the geo-origin of the DNS request we resolve to different load balancers. Then the websocket connection is made and stays on that instance until its closed.
#3
elmato API Nodes

wss://api.btsxchng.com

Architecture:


  • 3 Zones

    • Asia Pacific (Singapore)
    • US East (N. Virginia)
    • EU (London)
  • 3 Load balancers (one per zone)
  • 9 API nodes (3 per load balancer)
  • Traffic policies on geolocation (Asia/North America/Europe/Other)


PR
https://github.com/bitshares/bitshares-ui/pull/1399
#4
General Discussion / Re: review for price feeding
December 31, 2017, 04:21:44 AM


I've taken a deeper look at price feeds and now i think they are good shape.
Please consider voting @ElMato back to the active witness set.
#5
General Discussion / Re: review for price feeding
November 20, 2017, 09:14:15 AM
Quote from: bitcrab on November 18, 2017, 03:11:52 PM
hi, @ElMato @wackou @verbaltech2 could you please check your price feeding and update the script? your feeding price is far below the reasonable figure.

the price from poloniex need to be removed.





Feed prices are back, poloniex was removed from the equation
#6
Hi guys, as witness i agree with the changes and hardfork date
#7
Dear Alt, I've stopped feeding prices on purpose and started to write my own feed script, but its taking me longer so i will fallback to xeroc script with abit patch
#8
Quote from: bitcrab on March 06, 2017, 07:54:28 AM
@ElMato can you check? it seems your feeding price in bitCNY is much higher than the real market price.

It seems that i'm having problems getting prices from btc38/okcoin/huboi

Error fetching book from btc38!
Error fetching ticker from okcoin cn!
Error fetching ticker from huobi!
#9
Great work!!  +5%

Just one question.
Shouldn't we also have a local fork of this two repos?

https://github.com/zaphoyd/websocketpp.git
https://github.com/leutloff/diff-match-patch-cpp-stl

What happen if zaphoyd/leutloff got compromised in any way?
#10
Updated price feed for SILVER, GOLD and CNY.
witness name: elmato

#11
Cierto .. cuando quieran nos hablamos por telegram un rato y coordinamos acciones.
#12
General Discussion / Re: Transaction Throughput Testing
December 31, 2016, 09:51:56 AM
Im in, i will setup a VPS in Argentina and if i have some time also some scripts to generate spam txs

Sent from my XT1063 using Tapatalk

#13
Technical Support / Re: New API for witness_node
December 28, 2016, 01:42:00 AM
Quote from: abit on December 27, 2016, 03:46:47 PM
Just FYI that Steem has moved on to use a SQL database to store irreversible chain state data. More developer can benefit from using that model, as more people know SQL in comparison to C++.

Quote from: xeroc on December 26, 2016, 07:57:52 PM
Paging @vikram
I wonder why it's not clickable. Paging @vikram

//Edit:
It's true that it's not too hard (for me) to implement more API's and/or plugins .. but I don't have time to do it, nor discuss the details, sorry.


@abit, how steem will implement the SQL database for the irreversible state?
steemd will be pushing data to the SQL database? or an external process will be polling?

Last time i checked steem source code i didn't see any SQL plugin or something like that.

They will model every object as a table with their corresponding indexes?
Or a plain object_id->text(json) table with custom indexes as tables?


#14
Quote from: bilthon on December 22, 2016, 08:23:28 PM
Hello there, I'm trying to figure out exactly how to use the 'get_trade_history' database API call. The documentation seems to be a bit off for this one, since the order of the arguments displayed here http://docs.bitshares.org/api/database.html seems to be wrong.

Taking a look at the graphene code itself, I can find at /libraries/app/database_api.cpp:110 the following:

vector<market_trade> get_trade_history( const string& base, const string& quote, fc::time_point_sec start, fc::time_point_sec stop, unsigned limit = 100 )const;

But this is kind of at odds with what I actually find when querying the API, since it seems to be expecting a date format.

Connecting directly to a via wscat I get the following:

> {"id":1,"method":"call","params":[0,"get_trade_history",["BTS","EUR","20161215T0130000","20161212T233000", 100]],"jsonrpc":"2.0"}
< {"id":1,"result":[]}


And no, reverting the start and stop values doesn't seem to change anything either. Same result. Can anyone give me a hand with this?

Nelson
/**

* A lower resolution time_point accurate only to seconds from 1970

*/

  class time_point_sec

  {
...

From
https://github.com/cryptonomex/fc/blob/master/include/fc/time.hpp


Sent from my XT1063 using Tapatalk

#15
I wrote a post to see if we can join efforts in upgrading the API of the witness_node or build a parallel solution to query the blockchain state in any possible way.

https://bitsharestalk.org/index.php/topic,23627.0.html