BitShares Forum
Main => Stakeholder Proposals => Topic started by: openledger on April 12, 2017, 10:13:37 pm
-
Allow me to introduce to you all my OpenLedger team offering to support the BitShares network and using my initial account openledger-dc as the account for future settlement
We’re the OpenLedger tech team and we have 8 dedicated servers designed for supporting BitShares & OpenLedger ecosystem. Our system has DDOS protection, distributed between different geo locations and totally built according to security and resistance requirements of modern cryptoworld. More than that we have been working already for more than 2 years and have obtained significant experience and achieved some great uptime result.
Our proposal is to make our group of servers a reliable witness for making BitShares network stronger, more stable and secure.
The income from witness activity is planned to be used for further network distribution among the Asia and South-East regions.
Yours sincerely on behalf of the OpenLedger team
Ronny Boesing
CEO
OpenLedger ApS
Please vote for the openledger-dc witness node!
-
that's the way, welcome join the wintess
but I'm afraid your account is not upgrade to witness correct.
just need confirm:
1. can you make sure your witness node is already stand by?
2.are you ready to provide the feed price?
-
that's the way, welcome join the wintess
but I'm afraid your account is not upgrade to witness correct.
just need confirm:
1. can you make sure your witness node is already stand by?
2.are you ready to provide the feed price?
Sorry I promised the team to present tonight, they will get all done tomorrow from what I understood
-
That is great! I believe the platform needs a strong pool of witnesses both standby and active.
I would be interested in seeing the witness proposal from your technical team on how exactly do you plan to deploy the 8 servers? Are you talking about running nodes on each one of them?
-
Those servers are running, most clients is connecting to their api nodes.
-
Can I make the request that your dev teams first setup a witness node on the testnet and have it running there for a few weeks so they know what they are dealing with?
-
Howdy!
My name is Ivan, i’m dev behind the OpenLedger project.
Wanted to introduce infrastructure, we’ve made already:
EU location:
- 2 frontend servers, working as entry points, but binded between eachother via round-robin algo. It excludes situations, when D(DOS) attacks are starting on one of them (within a reasonable scales).
- 4 backend servers, working with graphene nodes (from 2 to 6 on each server are running constantly). Also, there is dynamic balancing, depending on processing loads.
CN location:
- 1 server for frontend
- 1 server for backend
Specifications of EU servers:
Intel Xeon E5-1650 v3 Hexa-Core
128gb ddr4 ecc RAM.
1 Gbit/s bandwidth
For now, we’re going to present EU witness node, support its performance and continue network development.
@xeroc, we really understand importance of supporting testnet also, so during weekends we've started testnet witness. Made also at account openledger-dc. Could u please vote for this also, for checking its performance?
@alt, thanks. Account is already upgraded. We're going to launch feeds asap, need to understand this correct.
@sahkan, for users, mostly, these servers look like union, with the only, but stable entry point, having significant resistance. Everything automatized behind the frontend.
Thanks everyone for supporting. We really hope for your voting for witness account: openledger-dc
Will be glad to provide details and response on any questions.
Best Regards, Ivan
-
@xeroc, we really understand importance of supporting testnet also, so during weekends we've started testnet witness. Made also at account openledger-dc. Could u please vote for this also, for checking its performance?
Do you plan to become also a committee member on test net?
-
Do you plan to become also a committee member on test net?
Yeah, nice idea. Will do asap. There will be openledgerdc account for committee.
Will appreciate for votes on this.
-
@xeroc, we really understand importance of supporting testnet also, so during weekends we've started testnet witness. Made also at account openledger-dc. Could u please vote for this also, for checking its performance?
Done.
-
You already got my vote. The workload is increasing on the witnesses and we need a future-ready infrastructure.
-
Has anyone looked at @wackou's plans to implement this configuration (http://digitalgaia.io/backbone.html)?
I know he was waiting on a few pull requests to be merged before it was possible but I'm fairly certain those are now in place.
I suspect there will be increased risk of attack as with the upsurge in traffic. This scheme could help shield the witness nodes by only connecting to seed nodes and letting the public his the seeds and not witness nodes directly.
Wackou and I talked about this late 2015 early 2016, but he has been extremely busy, not to mention until the last month things were pretty quiet.
-
Voted, support openledger! +5%
-
Weekly updates.
1) We’ve started to publish feeds on testnet under the openledger-dc account. It's similar implementation of bitUSD, bitEUR, bitCNY, but named in testnet, accordingly, testUSD, testEUR, testCNY.
(https://openledger.info/assets/images/witness/testfeeds.jpg)
2) Recently, feeds publishing for MPA RUBLE had been started from openledger-dc account on production network. We strongly believe in potential of bringing russian market into DEX.
(https://openledger.info/assets/images/witness/rublefeeds.jpg)
3) We have prepared and tested scripts aimed to provide bitUSD/bitEUR/bitCNY feeds. Ready to provide feeds on any number of MPA - just suggest in the comments or write me directly.
4) To be continued...
Thanks to everyone, who has voted for us. With your help, we’re much closer to active status.
Let’s make the DEX great again soon ASAP! :)
P.S. And still, we really hope on your vote for openledger-dc, dear Friend. Will appreciate...
-
Excellent news!
-
+5%
Great, OpenLedger joined the witness team.
As a Digital Asset Exchange running on BitShares, I believe you will be more responsible for system security.
I'm a proxy, you have my vote!
Voting status will be updated in 16:00 ( UTC+8 ).
-
@Yao, @ripplexiaoshan, thank you very much, guys!
@xeroc, we're also opened for any tests/collaborations on testnet, as well, as on production - just let me know. We have performances, infrastructure and healthy curiosity.
-
Welcome!
Definitely vote for u.
-
In order to obtain a slot as feed producer, please send an email to::: feed@hero.global
http://docs.hero.global/en/master/feedproducer.html
would be cool if you'd join the feeding :)
-
@Yao, @ripplexiaoshan, thank you very much, guys!
@xeroc, we're also opened for any tests/collaborations on testnet, as well, as on production - just let me know. We have performances, infrastructure and healthy curiosity.
Please add way to export trade history or a P&L page like polo. The recent trade export doesn't export all trades. Thanks!
Also some activity graphs would be nice, like some way to track total OL trades / fee earnings for the month LIVE for those of us who hold OBITS.
-
Hey @ccedk, could you please begin publishing price feeds for the 'Hertz' asset? I would massively appreciate your support.
Hertz (Hz) is a Algorithm Based Asset (ABA) which is pegged against the USD and modified to oscillate using a sine wave, thus we are able to create potential phases of buying and selling pressure.
Important Smartcoin settings:
- Maintenance collateral ratio (MCR): 175%
- Maximum short squeeze ratio (MSSR): 150%
- Max feed lifetime: 1440
- Delay for forced settlements (minutes): 720
- Percent offset of forced settlements: 1%
- Min number of feeds: 7
Properties of Hertz (Hz):
- Amplitude: 14% (NOT 33% nor 50% - It was changed to 14% for the first HERTZ asset).
- Period: 28 days.
- Daily price feed change: 1% per day.
- Max price feed rate: $1.14
- Min price feed rate: $0.86
Price feed scripts:
- Reference scripts & calculator: https://github.com/BTS-CM/scripts (https://github.com/BTS-CM/scripts)
- Wackou's 'BTS_Tools' (Only use once pull request #36 is merged): https://github.com/wackou/bts_tools/pull/36 (https://github.com/wackou/bts_tools/pull/36)
- Xeroc's 'Bitshares-PriceFeed': https://github.com/xeroc/bitshares-pricefeed (https://github.com/xeroc/bitshares-pricefeed)
http://open-explorer.io/#/assets/HERTZ
Many thanks,
CM.
-
Just created a ticket on openledger freshdesk support requesting the openledger-dc witness begins publishing Hertz price feeds.
Cheers +5%