BitShares Forum

Main => Stakeholder Proposals => Topic started by: blockchained on May 02, 2017, 01:42:05 pm

Title: [Witness Proposal] blckchnd
Post by: blockchained on May 02, 2017, 01:42:05 pm
All further RuDEX announcements will be published in our official channels:

https://steemit.com/@rudex
https://golos.id/@rudex
https://twitter.com/team_rudex
https://t.me/RU_DEX


---

Those of you who are following the Bitshares platform certainly know about the recent event, that caused a lot of debate. During the BTS4.0 protocol upgrade, one of the hired core devs (abitmore) added a community unapproved backdoor to the code, which led to the change of the voting rights, and a major change of the consensus procedure. As a result multiple conflicts ensued with a significant portion of chinese community leaving Bitshares.

After thoroughly analysing the consensus changes, that were made without voting or any discussion by community members, we verified that the resulting system is unscalable and doomed to stagnate. As a result our team decided to launch a fork of stable and time tested Bitshares3.0 consensus code using Graphene — the original name of the technology.


UPD:

Good news, everyone!

The time has come! As we have repeatedly declared in our public chats and on the forum, RuDEX is migrating from Bitshares blockchain to Graphene (https://gph.ai/)

Migration is planned starting from 12:00 MSK 24.05.2021 (Mon) to 12:00 MSK 27.05.2021 (Thu). Please note that it will take THREE FULL DAYS! During this time all RuDEX gateways will be disabled for deposit/withdrawal, as well as transfer will be disabled for all RuDEX assets on Bitshares.

Such duration is due to the necessity to scan Bitshares blockchain to gather required data to swap RuDEX UIA assets from Bitshares blockchain to RuDEX UIA assets on Graphene blockchain.

After migration the deposits/withdrawals will be restored in full but using Graphene blockchain.

Most public services provided by RuDEX for Bitshares blockchain will be disabled, and there are no plans to enable them in the future.

Assets on RuDEX accounts are eligible for swap if their amount is equal or greater than the minimum amount for gateway withdrawal, information about the minimum limits is available at audit page.

P.S. To access Bitshares using our platform we will keep old.rudex.org domain, you will be able to use it to access your tokens on Bitshares platform that are not issued by RuDEX. We would like to note that this DNS address will work only as an access point and registration faucet, all other services for Bitshares blockchain will be disabled.

Thank you for your time, and we’ll see you on the other side!
Team RuDEX

Title: Re: [Witness Proposal] blckchnd
Post by: sahkan on May 02, 2017, 03:27:57 pm
 +5%
Title: Re: [Witness Proposal] blckchnd
Post by: alt on May 03, 2017, 03:59:16 am
great
have voted for you
Title: Re: [Witness Proposal] blckchnd
Post by: Yao on May 03, 2017, 07:11:30 am
 +5% Incredible Russian team! Your execution make people sit up and take notice. :D
BitShares community need more team like you, we will once again brilliant!

I'm a proxy, you have my vote!
Title: Re: [Witness Proposal] blckchnd
Post by: xeroc on May 03, 2017, 08:51:03 am
+5%
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on February 06, 2018, 12:00:54 am
Monthly witness report for blckchnd №1 and RuDEX update

Welcome!
In the spirit of making our activity more transparent we’ve decided to start publishing monthly reports on our work as a Bitshares witness. Start of the new year is a good time to start doing it, since it is a milestone that you can look back from and see that a lot of small steps resulted in a long journey.

If you like what we’re doing, you can support us by voting for our witness blckchnd

Technical work

We've been supporting an interrupted service of our access point for Bitshares DEX in RuDEX with the following technical park

This month due to the significantly increased load we’ve added two additional servers for full API nodes (one public, one for our internal use):

- Type: Dedicated
- Processor: Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
- Cores: 4
- Ram: 128 GB DDR3
- 2 x 220 GB SSD
- Connection: 1 Gbit/s
- Location: Germany

We also support gateway for Steem, Golos, Peerplays, Muse, and recently for Karma and Decent

Additionally we’re active in bitshares github, including pull requests and bug reports. You can track our activity here https://github.com/blckchnd

Awareness and outreach activities

We’ve started this as an awareness and outreach mission, that we’re diligently working on to this day.
Other than creating and maintaining first Russian interface for Bitshares, our team has translated and published several hundred articles about Bitshares Dex, including weekly State of the Network reports that are produced by steempower
In last three months the number of such articles was over fifty, with 17 of them published during December 2017.
You can see them in more detail by looking at our blog on Steemit http://bit.ly/2qouC3r

As part of our mission to bring Graphene technology to mass awareness and acceptance we’ve presented Bitshares and RuDEX at X conferences in St. Petersburg and Moscow (not counting our participation in SteemFest and SteemFest2).

(https://s18.postimg.org/8hj5u5xux/photo_2018-01-30_21-26-49.jpg)

(https://s18.postimg.org/4xx84dq09/image_2018-01-30_22-48-25.png)

For the same reason we’ve also created and are moderating Russian language developer chats.
We’re also actively moderating Russian language threads on bitcointalk https://bitcointalk.org/index.php?topic=1875875.0, which is now more than 15 pages in length (18,5k views).

We’ve requested TradingView to add Bitshares DEX into the exchange list, and you can support this by liking and commenting on this thread https://getsatisfaction.com/tradingview/topics/addition-of-bitshares-based-decentralized-exchange-s.

On top of that we’re helping several teams that are working on creating their own interfaces and/or businesses based on Bitshares DEX.
It seems that our bad influence is contagious. :)

RuDEX update

A new version of RuDEX clients for Windows/Linux/macOS is available at our Github here: https://github.com/blckchnd/rudex-ui/releases

Thank you for your time, now we can get back to work, since our moto is less talk, more action.

- Team RuDEX

Vote for our witness: blckchnd

(https://steemitimages.com/DQmZ93AKoCqWU9sE3mpZcQdvLTznU4af1ALN8HjfrBN9f2d/%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5.png)

Title: Re: [Witness Proposal] blckchnd
Post by: yvv on February 06, 2018, 01:16:43 am
Very good job guys. Rudex ATM is great, hope you will spread to outside of capitals.
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on March 12, 2018, 07:38:52 pm
Monthly witness report for blckchnd №2 and RuDEX update can be found HERE (http://bit.ly/2Gj5qRr)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on March 13, 2018, 08:41:21 pm
TravelChain (TT) gateway with 0% fees for decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (http://bit.ly/2FzB1Bo)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on March 26, 2018, 09:22:57 pm
Scorum (SCR) gateway with 0% fees for decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2DXo26D)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on April 10, 2018, 03:56:22 pm
Monthly witness report for blckchnd №3 and RuDEX update can be found HERE (https://bit.ly/2qmQjQf)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on April 24, 2018, 05:26:26 pm
Ethereum (ETH) gateway for decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2Hu8Occ)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on May 17, 2018, 09:38:44 pm
Bitcoin (BTC) gateway for decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2IKyxki)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on May 19, 2018, 01:36:45 pm
Digibyte (DGB) gateway for decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2IuSAnH)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on June 25, 2018, 11:43:32 am
EOS gateway for decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2MnO9Z4)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on July 04, 2018, 07:02:20 pm
Witness report for blckchnd №4 and RuDEX update can be found HERE (https://bit.ly/2KPrIMi)
Title: Re: [Witness Proposal] blckchnd
Post by: bench on July 17, 2018, 04:59:36 pm
Any plans on adding a Bitcoin Cash gateway?
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on September 08, 2018, 05:40:16 pm
Peercoin (PPC) gateway on decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2Mbq2fW)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on September 08, 2018, 05:42:02 pm
Any plans on adding a Bitcoin Cash gateway?

we have a plan to give the community a tool to vote for the gateways we add
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on September 22, 2018, 03:21:36 pm
Gridcoin (GRC) gateway on decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2Nyc8K4)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 04, 2018, 05:13:06 pm
SMOKE gateway on decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2PczoKu)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 09, 2018, 04:23:36 pm
Whaleshares gateway on decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/2OLOVEe)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 20, 2018, 06:19:00 pm
TT (Travelchain) Delisting Announcement can be found HERE (https://bit.ly/2yQ0Q9Y)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on November 21, 2018, 08:32:25 pm
Announcement of a public trading bots from RuDex: SpreadTrade and TrailingStop can be found HERE (https://bit.ly/2QfWx2o)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on December 04, 2018, 01:01:47 am
Blckchnd 2018 Q3 Witness report can be found HERE (https://bit.ly/2KQRq3B)
Title: Re: [Witness Proposal] blckchnd
Post by: btspp on December 04, 2018, 02:36:37 am
Blckchnd 2018 Q3 Witness report can be found HERE (https://bit.ly/2KQRq3B)

Nice work.
Hello blckchnd
Can you look at our worker proposal?
If you feel good, I hope you can vote for us.
Forum: https://bitsharestalk.org/index.php?topic=27486.0
Thank you~
Title: Re: [Witness Proposal] blckchnd
Post by: yamtt on December 04, 2018, 05:04:31 pm
That's the witness we need
Title: Re: [Witness Proposal] blckchnd
Post by: sschiessl on December 04, 2018, 07:09:49 pm
Thank you very much for the report!
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on December 26, 2018, 05:39:54 pm
PPC & DCT Delisting Announcement can be found HERE (https://bit.ly/2T77AJ4)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on January 01, 2019, 05:05:57 pm
Rudex Market fee changes
- golos - 0.05%
- gbg - 0.05%
- steem - 0.05%
- sbd - 0.05%
- scorum - 0.05%
- eos -0.05%
- whaleshares - 0.05%
- viz - 0.05%


more information can be found HERE (https://bit.ly/2s3uqFZ)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on January 02, 2019, 03:03:38 pm
MUSE Delisting Announcement can be found HERE (https://bit.ly/2LNAThp)
Title: Re: [Witness Proposal] blckchnd
Post by: xeroc on January 05, 2019, 01:10:42 pm
was about time for you to earn some income for you hard work!
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on January 25, 2019, 06:01:36 pm
DGB Delisting Announcement can be found HERE (https://bit.ly/2MxDdJR)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on February 07, 2019, 07:46:02 pm
Rudex market fee changes more info can be found here: https://steemit.com/rudex/@blockchained/rudex-market-fee-changes
Title: Re: [Witness Proposal] blckchnd
Post by: sschiessl on February 07, 2019, 10:04:37 pm
Link broken, also the link is already hidden in text, shortening not needed
Title: Re: [Witness Proposal] blckchnd
Post by: Thul3 on April 05, 2019, 07:03:22 am
Hi blockchained could you please have a look at your MSSR for bitcny.
Its currently 1.05 and should be 1.02
Title: Re: [Witness Proposal] blckchnd
Post by: bitProfessor on April 06, 2019, 07:57:00 am
Hi blockchained could you please have a look at your MSSR for bitcny.
Its currently 1.05 and should be 1.02
thank you
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on April 11, 2019, 07:26:41 pm
Hi blockchained could you please have a look at your MSSR for bitcny.
Its currently 1.05 and should be 1.02

Hi
thanks, for reminding
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on June 21, 2019, 02:23:25 pm
Announcement of a new public trading bot from RuDex: PercentUP

Hello, RuDEX users & Bitshares community!

We are continuing to expand the stable of RuDEX trading bots, and are glad to present to you a new PercentUp strategy, that was just added to the bots section, that also has SpreadTrade and TrailingStop

Our opinion is that the public bots are critical to the business development of the DEX and increase of liquidity by automating routine actions, and that is why we're offering such instruments for you.

If you also want that robots would perform all the work for you, please watch the following video about the new PercentUp strategy and test it out on the exchange!

https://www.youtube.com/watch?v=SGXbmjXfrks&feature=youtu.be (https://www.youtube.com/watch?v=SGXbmjXfrks&feature=youtu.be)

Due to some causes that we're not clear about, RuDEX recently lost our position at the top of Witness list due to a sudden revocation of a lot of votes for us, and if you like what we're doing and want us to continue developing and maintaining our services, we're asking you to vote for our witness blckchnd. This is really important for the independence of our team
Title: Re: [Witness Proposal] blckchnd
Post by: binggo on September 30, 2019, 07:57:39 am
Please Check your MSSR in bitcny.
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on November 27, 2019, 05:10:10 pm
KRM & GRC Delisting Announcement can be found HERE (https://bit.ly/2QUwgqs)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on December 02, 2019, 11:00:52 pm
SBD & GBG Delisting Announcement can be found HERE (https://bit.ly/2Y7ktqr)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on December 03, 2019, 04:23:46 pm
Tether (USDT) gateway on decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/34LCJIf)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on March 11, 2020, 09:48:10 pm
 Token listing on RuDEX is open for everyone!: https://steempeak.com/rudex/@rudex/token-listing-on-rudex-is-open-for-everyone
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on April 17, 2020, 06:18:49 pm
PRIZM (PZM) gateway on decentralized trading platform Bitshares RuDEX launched announcement can be found HERE (https://bit.ly/3blum9y)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on July 13, 2020, 02:48:10 pm
Hello everyone!
 
Today we are finally ready to present you our latest localization of open source development based on the Bitshares blockchain – it is the RuDEX mobile app for Android!
It’s already available for download in the Google Play Store (https://play.google.com/store/apps/details?id=org.rudex.app) right now.

This is an improved version of widely known in the Bitshares community bitshares-mobile-app (https://github.com/bitshares/bitshares-mobile-app), developed by an independent team with community funding. We created a special RuDEX gateway localization for it and thoroughly adapted it for the maximum ease of use of this product.

Current version of RuDEX mobile app includes the following functions:

- Registering new accounts, logging in with existing ones and back up support
- Account mode and wallet mode support
- Multi-account support
- Viewing all assets and trading in Bitshares markets
- Encrypted stealth transactions (blind transfers)
- Markets, chart, K-line chart, trading history
- Margin trading
- Account search, feed price information, margin position rating
- Sending and receiving tokens
- Issuing and managing of your assets based on Bitshares
- Token deposit/withdrawal
- Voting and government of Bitshares DAC
- FAQ


We also couldn’t miss the opportunity to remind you of some benefits of RuDEX in comparison with centralized exchanges:

- Ability to trade fully decentralized assets
- Multi-language interface and support
- Desktop applications for all major OS
- Full exclusive control over your own account and funds
- The impossibility of blocking the trading platform and the Bitshares blockchain
- Correspondence of the amount of asset tokens to their actual amount in the gateway wallet
- Transparency for audit (https://audit.rudex.org)


Join trading on RuDEX – the mobile application makes it even easier!

In addition, our team is currently preparing a number of interesting updates to existing services that will not disappoint you. Subscribe to our blog to don’t miss updates and other news.

Have a good trade!
Title: Re: [Witness Proposal] blckchnd
Post by: kenCode on July 18, 2020, 03:42:36 pm
Join trading on RuDEX – the mobile application makes it even easier!

Dima, you guys are so awesome!!!
The app looks gorgeous and Bitshares is extremely lucky to have your business services offered on this chain.
Thank you for all of your continued hard work over the years.
 
If you guys ever start your own chain (no KYC of course) please let us know on PalmPay.chat and thanx again!!  8) 8)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on July 22, 2020, 12:32:29 pm
Join trading on RuDEX – the mobile application makes it even easier!

Dima, you guys are so awesome!!!
The app looks gorgeous and Bitshares is extremely lucky to have your business services offered on this chain.
Thank you for all of your continued hard work over the years.
 
If you guys ever start your own chain (no KYC of course) please let us know on PalmPay.chat and thanx again!!  8) 8)

thank you for your feedback
Title: Re: [Witness Proposal] blckchnd
Post by: binggo on July 30, 2020, 08:28:03 am
Will have new chain? Sounds great! :)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on July 30, 2020, 07:25:27 pm
Will have new chain? Sounds great! :)

 I heard that some teams experiment with such idea. I guess Ken meant this
Title: Re: [Witness Proposal] blckchnd
Post by: kenCode on August 01, 2020, 06:03:57 pm
Will have new chain? Sounds great! :)

I heard that some teams experiment with such idea. I guess Ken meant this

I prefer to stay here at Bitshares, and help to build the brand here, but if this whale war continues to destroy Bitshares' reputation I see no other choice but to move our apps to a fork so that we can finally move forward again. Decaying votes' implementation and removal of custodial voting though seems like a good step in the right direction, so I still have faith :)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 05, 2020, 02:40:37 pm
Hello everyone!
 
Today we are finally ready to present you our latest localization of open source development based on the Bitshares blockchain – it is the RuDEX mobile app for Android!
It’s already available for download in the Google Play Store (https://play.google.com/store/apps/details?id=org.rudex.app) right now.

This is an improved version of widely known in the Bitshares community bitshares-mobile-app (https://github.com/bitshares/bitshares-mobile-app), developed by an independent team with community funding. We created a special RuDEX gateway localization for it and thoroughly adapted it for the maximum ease of use of this product.

Current version of RuDEX mobile app includes the following functions:

- Registering new accounts, logging in with existing ones and back up support
- Account mode and wallet mode support
- Multi-account support
- Viewing all assets and trading in Bitshares markets
- Encrypted stealth transactions (blind transfers)
- Markets, chart, K-line chart, trading history
- Margin trading
- Account search, feed price information, margin position rating
- Sending and receiving tokens
- Issuing and managing of your assets based on Bitshares
- Token deposit/withdrawal
- Voting and government of Bitshares DAC
- FAQ


We also couldn’t miss the opportunity to remind you of some benefits of RuDEX in comparison with centralized exchanges:

- Ability to trade fully decentralized assets
- Multi-language interface and support
- Desktop applications for all major OS
- Full exclusive control over your own account and funds
- The impossibility of blocking the trading platform and the Bitshares blockchain
- Correspondence of the amount of asset tokens to their actual amount in the gateway wallet
- Transparency for audit (https://audit.rudex.org)


Join trading on RuDEX – the mobile application makes it even easier!

In addition, our team is currently preparing a number of interesting updates to existing services that will not disappoint you. Subscribe to our blog to don’t miss updates and other news.

Have a good trade!


RuDEX Mobile v6.2 update

What's new?   
1. Added the function of staking voting.   
2. Add the entry of STAKE in my asset interface.   
3. Fix some bugs.

Title: Re: [Witness Proposal] blckchnd
Post by: binggo on August 05, 2020, 11:24:53 pm
Hello everyone!
 
Today we are finally ready to present you our latest localization of open source development based on the Bitshares blockchain – it is the RuDEX mobile app for Android!
It’s already available for download in the Google Play Store (https://play.google.com/store/apps/details?id=org.rudex.app) right now.

This is an improved version of widely known in the Bitshares community bitshares-mobile-app (https://github.com/bitshares/bitshares-mobile-app), developed by an independent team with community funding. We created a special RuDEX gateway localization for it and thoroughly adapted it for the maximum ease of use of this product.

Current version of RuDEX mobile app includes the following functions:

- Registering new accounts, logging in with existing ones and back up support
- Account mode and wallet mode support
- Multi-account support
- Viewing all assets and trading in Bitshares markets
- Encrypted stealth transactions (blind transfers)
- Markets, chart, K-line chart, trading history
- Margin trading
- Account search, feed price information, margin position rating
- Sending and receiving tokens
- Issuing and managing of your assets based on Bitshares
- Token deposit/withdrawal
- Voting and government of Bitshares DAC
- FAQ


We also couldn’t miss the opportunity to remind you of some benefits of RuDEX in comparison with centralized exchanges:

- Ability to trade fully decentralized assets
- Multi-language interface and support
- Desktop applications for all major OS
- Full exclusive control over your own account and funds
- The impossibility of blocking the trading platform and the Bitshares blockchain
- Correspondence of the amount of asset tokens to their actual amount in the gateway wallet
- Transparency for audit (https://audit.rudex.org)


Join trading on RuDEX – the mobile application makes it even easier!

In addition, our team is currently preparing a number of interesting updates to existing services that will not disappoint you. Subscribe to our blog to don’t miss updates and other news.

Have a good trade!


RuDEX Mobile v6.2 update

What's new?   
1. Added the function of staking voting.   
2. Add the entry of STAKE in my asset interface.   
3. Fix some bugs.

 8)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 25, 2020, 02:47:30 pm
One more abuse of admin rights in a telegram from the well-known abuser abit
I was muted by him in the chat with no reason and no explanation by his private bot.
His bot ban a lot of independent admins to silence them
Abit well known in our community as a fraudster for his bsips so no surprise.
Title: Re: [Witness Proposal] blckchnd
Post by: abit on August 25, 2020, 03:27:53 pm
Thanks to your friend Thule.

(https://user-images.githubusercontent.com/9946777/91193920-fdf19500-e6f7-11ea-9661-e41fb4601580.png)
(https://user-images.githubusercontent.com/9946777/91193917-fd58fe80-e6f7-11ea-8c2d-92b98cd11e93.png)
(https://user-images.githubusercontent.com/9946777/91193913-fc27d180-e6f7-11ea-9c99-de536506687d.png)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 25, 2020, 03:38:15 pm
Thanks to your friend Thule.

(https://user-images.githubusercontent.com/9946777/91193920-fdf19500-e6f7-11ea-9661-e41fb4601580.png)
(https://user-images.githubusercontent.com/9946777/91193917-fd58fe80-e6f7-11ea-8c2d-92b98cd11e93.png)
(https://user-images.githubusercontent.com/9946777/91193913-fc27d180-e6f7-11ea-9c99-de536506687d.png)

cool, finally someone forced you to eat the same dish,
you are abuser abit, you lost your ethic, you silently banned admins long before thulee decide to react,  I can witness that

So you first started this dictatorship in the chat with silent bans by your bot for opinion against your agenda


Is this some kind of Chinese tradition to punish everyone around without any proof or excuse?


Poor abit you really look miserable in your fall

you just a criminal and deserve what will come to you

   
Title: Re: [Witness Proposal] blckchnd
Post by: abit on August 25, 2020, 04:20:25 pm
You just removed all messages from only 12 people. You can do better.

(https://user-images.githubusercontent.com/9946777/91200289-46608100-e6ff-11ea-9498-a9f4f7eeed28.png)
(https://user-images.githubusercontent.com/9946777/91200293-4791ae00-e6ff-11ea-85a8-8406de7e4fdc.png)
(https://user-images.githubusercontent.com/9946777/91200296-482a4480-e6ff-11ea-93e2-762dc1c7dad1.png)
(https://user-images.githubusercontent.com/9946777/91200297-48c2db00-e6ff-11ea-9721-ff5126105d06.png)
(https://user-images.githubusercontent.com/9946777/91200300-495b7180-e6ff-11ea-8a62-9e0c1da1fafd.png)
(https://user-images.githubusercontent.com/9946777/91200302-495b7180-e6ff-11ea-992c-bb2f55c14904.png)
(https://user-images.githubusercontent.com/9946777/91200306-49f40800-e6ff-11ea-97ad-a070011f9894.png)
(https://user-images.githubusercontent.com/9946777/91200309-4a8c9e80-e6ff-11ea-95ae-47ba1cdca3c5.png)
(https://user-images.githubusercontent.com/9946777/91200310-4b253500-e6ff-11ea-8739-c439714a05e3.png)
(https://user-images.githubusercontent.com/9946777/91200313-4b253500-e6ff-11ea-919f-4cdedb1e74b5.png)
(https://user-images.githubusercontent.com/9946777/91200315-4bbdcb80-e6ff-11ea-8e31-f26e22ba0475.png)
(https://user-images.githubusercontent.com/9946777/91200316-4c566200-e6ff-11ea-909e-0050a82ebcba.png)
Title: Re: [Witness Proposal] blckchnd
Post by: abit on August 25, 2020, 04:23:40 pm
By the way,
(https://user-images.githubusercontent.com/9946777/91200830-f635ee80-e6ff-11ea-8644-27eea186b9ff.png)
Title: Re: [Witness Proposal] blckchnd
Post by: abit on August 25, 2020, 04:25:30 pm
Thanks to your friend Thule.

(https://user-images.githubusercontent.com/9946777/91193920-fdf19500-e6f7-11ea-9661-e41fb4601580.png)
(https://user-images.githubusercontent.com/9946777/91193917-fd58fe80-e6f7-11ea-8c2d-92b98cd11e93.png)
(https://user-images.githubusercontent.com/9946777/91193913-fc27d180-e6f7-11ea-9c99-de536506687d.png)

cool, finally someone forced you to eat the same dish,
you are abuser abit, you lost your ethic, you silently banned admins long before thulee decide to react,  I can witness that

So you first started this dictatorship in the chat with silent bans by your bot for opinion against your agenda


Is this some kind of Chinese tradition to punish everyone around without any proof or excuse?


Poor abit you really look miserable in your fall

you just a criminal and deserve what will come to you
Marked.
Title: Re: [Witness Proposal] blckchnd
Post by: abit on August 25, 2020, 04:50:09 pm
(https://user-images.githubusercontent.com/9946777/91205231-80cd1c80-e705-11ea-887f-efba054afd2d.png)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 25, 2020, 05:52:58 pm



abit you are criminal and deserve a jail

you started this shit with bots, I even don't have the right to add one

But if thuleee baned you by your own methods, he have my support

You are a cancer of bitshares
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 25, 2020, 05:54:19 pm

don't forget to add that you muted me and other admins first and deleted all history first, this was just reaction on your abuse

everyone could check the time who started this mess

(https://i.imgur.com/F8gzUDU.png)

(https://i.imgur.com/KQVYhwj.png)
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 25, 2020, 05:55:17 pm

all this sentence are addressed to you and fits you very well, you deserve each word and more
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 25, 2020, 05:57:53 pm
Thanks to your friend Thule.

cool, finally someone forced you to eat the same dish,
you are abuser abit, you lost your ethic, you silently banned admins long before thulee decide to react,  I can witness that

So you first started this dictatorship in the chat with silent bans by your bot for opinion against your agenda


Is this some kind of Chinese tradition to punish everyone around without any proof or excuse?


Poor abit you really look miserable in your fall

you just a criminal and deserve what will come to you
Marked.

your fraud and abuse of the system will be soon widely known, so just enjoy the ride fraudster


Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 25, 2020, 07:40:07 pm
Thanks to your friend Thule.


You still didn't answer me what I'm to do with this bot, why you mute me?
Or you mute gateway owner that produces fees and bring users and volume, just because I support thuleee opinion that criticize your behavior? 
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on August 29, 2020, 10:35:46 am
From this moment RuDEX team stop to participate in this forum.
This forum occupied with admins that abuse their admin power and supports malicious actions with Github.
All further RuDEX announcements will be published in our official channels:

https://steemit.com/@rudex
https://golos.id/@rudex
https://twitter.com/team_rudex
https://t.me/RU_DEX
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on September 29, 2020, 02:55:47 pm
After abit trojan took place yesterday we've stopped our witness infrastructure for bitshares.

We have a capable team of core and UI devs, so we're preparing a fork of bitshares code base, back to the consensus rules that was before the abit abuse on github.
It will be a new distribution, a new chain, and a new genesis.
 
News will come latter with announcements.

 
Title: Re: [Witness Proposal] blckchnd
Post by: alt on October 02, 2020, 02:31:29 am
It's so bad to see you decide to step away too.
I respect you and wish you have a good process.

But if it's possible, May I  ask you to stay with Bitshares for more time?
Too many big argument the community have made recent years, but they are not a big deal indeed compare today.
People come and go, Bitshares is still here, you should stay with it if you still have faith in it.

You have development team, please step in the core development work.
Your business is the exchange gateway, pay more attention to the crypto asset instead of smart coin.
we can have more opportunity if we stay together than fork alone.

I still have faith in Bitshares, wish you too.

After abit trojan took place yesterday we've stopped our witness infrastructure for bitshares.

We have a capable team of core and UI devs, so we're preparing a fork of bitshares code base, back to the consensus rules that was before the abit abuse on github.
It will be a new distribution, a new chain, and a new genesis.
 
News will come latter with announcements.
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 02, 2020, 11:34:33 am
It's so bad to see you decide to step away too.
I respect you and wish you have a good process.

We've observed and supported this project for the last four years. But the last events that happened force us to do this step.
We can't tolerate github abuse from one core dev
We can't tolerate trojan that was delivered by audit worker
We can't tolerate broke of consensus that was publicly acknowledged by core manager Milos
We can't tolerate the staking mechanism that was enforced with 0 discussions and completely changed consensus and voting behavior
The staking problem that was implemented with no discussion and I guess without any modulation is that it's not scalable and it hit hard by "voting apathy" because you have no intention in staking, you gain nothing besides the "governance drama"
The "abit precedent" vanished any trust in the current blockchain consensus & witnesses and operating on it can be just not safe.
Even if everyone starts to play with his staking rules what guarantee we have that he will not abuse github again and broke consensus again? This is a rhetorical question.
 
But if it's possible, May I  ask you to stay with Bitshares for more time?
As a RuDEX gateway and registration-faucet and services we will be here if it is profitable for us, but I know the plans of current core group to enforce KYC on gateways and double tax the gateways assets and gateways liquidity, if this happens in this case we will migrate.

Too many big argument the community have made recent years, but they are not a big deal indeed compare today.
People come and go, Bitshares is still here, you should stay with it if you still have faith in it.
Never before was this kind of admin power abuse in Bitshares, so it's not about "people come and go" it's about safety.
Big part of Chinese community already split, but they also forked 4.0 code.
We believe not in Bitshares as a brand name or so, we like the tool that was before 4.0, with liquid voting and without double taxation, and this code doesn't exist now not in bitshares not in newshares. So we have no choice than start a new chain in attempt to save the tool in form we liked it.


You have development team, please step in the core development work.
We saw attempts that was blocked, abit refused give up his position in github and after his abuse I have no reason to work with dev with such ethics, so I don't understand how you plan to put someone besides him there?


Your business is the exchange gateway, pay more attention to the crypto asset instead of smart coin.

Sad true, but bitshares already not unique with UIA, so already exist better alternatives in this case,
Decentralization is a product and abit just broke this product made voting participation even less. 5% in dpos is really looks like a joke

we can have more opportunity if we stay together than fork alone.

I still have faith in Bitshares, wish you too.
Like I stated above we have a faith in the tool not in the brand name, but with the consensus that doesn't exist now, it is one of the reasons for our attempt to save this tool.
Only this way we can fix a reviving hole, and other mistakes that will never be fixed here because of a greed.

But if you have an idea how to fix bitshares issue with lack of trust to current situation don't hesitate to shoot me PM
If you have plan to fight back abit abuse we will support it too, we have a big server park so if the situation in bitshares changes it not hard to start rudex block producer here,

but as a blckchnd team we will work on a new chain to save a tool we fell in love, welcome btw.
Title: Re: [Witness Proposal] blckchnd
Post by: alt on October 02, 2020, 01:18:13 pm
We've observed and supported this project for the last four years. But the last events that happened force us to do this step.
We can't tolerate github abuse from one core dev
We can't tolerate trojan that was delivered by audit worker
We can't tolerate broke of consensus that was publicly acknowledged by core manager Milos
We can't tolerate the staking mechanism that was enforced with 0 discussions and completely changed consensus and voting behavior
The staking problem that was implemented with no discussion and I guess without any modulation is that it's not scalable and it hit hard by "voting apathy" because you have no intention in staking, you gain nothing besides the "governance drama"
The "abit precedent" vanished any trust in the current blockchain consensus & witnesses and operating on it can be just not safe.
Even if everyone starts to play with his staking rules what guarantee we have that he will not abuse github again and broke consensus again? This is a rhetorical question.

We saw attempts that was blocked, abit refused give up his position in github and after his abuse I have no reason to work with dev with such ethics, so I don't understand how you plan to put someone besides him there?

I agree all these things are ridiculous.
I think it's not a big deal to change to another official github address if we have enough vote power.
The real problem is it seems we are lack of reliable development team always, a team which truly serve the business.

I wish the business person include you and bitcrab and others can have more comunication, if you can reach a consensus, I will support with my vote.
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 02, 2020, 08:56:22 pm
I wish the business person include you and bitcrab and others can have more comunication, if you can reach a consensus, I will support with my vote.
不知道你是真傻还是装傻,还在幻想你口中所谓的 business person 来拯救你。
CryptoBridge OpenLedger SparkDEX 给的教训还不够吗?还有 Deex 之流就不说了。

就算掰开手指数现在还在 BitShares 的公司机构,
也要先看 Move Institute , XBTS , ioBanker , 甚至 BEOS 。
什么时候轮得到 RuDEX ? RuDEX 根本都不是注册公司。

RuDEX 有关联开发团队不假。社区出钱开发的btspp手机钱包,他换个皮就是自己的了。申请一个 UI worker 拿了一百万多万没做完。后来又想申请 core worker 拿钱,我说你先提交点代码让我看看,结果没声了。回头变成我不放权?

你的聪明才智哪里去了?一个 Thule 天天在你耳边吹风,就只有他说的才是真话?
不说别的。他说锁喂价好你就支持锁喂价。 RuDEX 完全是反对锁喂价的,他有没有和你说?
他天天黑巨蟹你没听见过?还幻想巨蟹和他和RuDEX合作。
醒醒。
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 02, 2020, 09:06:11 pm

I wish the business person include you and bitcrab and others can have more comunication, if you can reach a consensus, I will support with my vote.

再转点东西你看看。
什么样的一条链会被其它两条链控制?这算不算得上是币圈奇葩?认识不到这些还在那里妄谈什么共识呢?

什么样的人会对持异见者进行各种人身语言攻击,满口fuck呢?就因为作为网关就有了随心所欲fuck别人的权力?

alt你知道你在交谈的人在电报上是什么样的一副面孔吗?

这么多年得过且过,自欺欺人,掩耳盗铃式的面对问题,处理问题,你们希望能够得到一个什么样的好的结果?

个个票仓都跟嘉靖万历一样的,试问这条链能够有一个什么样的好结果呢?

一个国家难道也要给持有商务或者旅行或者游学签证的人投票权吗?

DPOS治理是不是贿选横行?你们有仔细想过或者试着去解决吗?

一条链只有什么是不可或缺的,是核心代币还是矿工?核心代币是不可或缺的吗?

一些人并没有追求如何使一条链的治理更公平、更合理,恰恰相反,他们在追求的是一种畸形的共识体系或者更加确切的说是利益作祟,他们不愿也不想看到在BM在DPOS上一些票权获得方式的迭代,

你们是否仔细想过,对一条链而言,核心代币票权治理真的合适吗?

我想大家都是成年人,有独立思考的能力,但是能够听信别人一遍遍的忽悠也算是一绝了。

连临时对代币的控制成本与时间成本都不想失去的人,能够做好与参与好什么样的治理?
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 12:43:00 am
I wish the business person include you and bitcrab and others can have more comunication, if you can reach a consensus, I will support with my vote.
不知道你是真傻还是装傻,还在幻想你口中所谓的 business person 来拯救你。
CryptoBridge OpenLedger SparkDEX 给的教训还不够吗?还有 Deex 之流就不说了。

就算掰开手指数现在还在 BitShares 的公司机构,
也要先看 Move Institute , XBTS , ioBanker , 甚至 BEOS 。
什么时候轮得到 RuDEX ? RuDEX 根本都不是注册公司。

RuDEX 有关联开发团队不假。社区出钱开发的btspp手机钱包,他换个皮就是自己的了。申请一个 UI worker 拿了一百万多万没做完。后来又想申请 core worker 拿钱,我说你先提交点代码让我看看,结果没声了。回头变成我不放权?

你的聪明才智哪里去了?一个 Thule 天天在你耳边吹风,就只有他说的才是真话?
不说别的。他说锁喂价好你就支持锁喂价。 RuDEX 完全是反对锁喂价的,他有没有和你说?
他天天黑巨蟹你没听见过?还幻想巨蟹和他和RuDEX合作。
醒醒。

so many lies from you abit,
you are pitty
Title: Re: [Witness Proposal] blckchnd
Post by: btstodamoon on October 03, 2020, 01:24:55 am
支持abit
Title: Re: [Witness Proposal] blckchnd
Post by: xixi002020 on October 03, 2020, 01:50:31 am
I wish the business person include you and bitcrab and others can have more comunication, if you can reach a consensus, I will support with my vote.
不知道你是真傻还是装傻,还在幻想你口中所谓的 business person 来拯救你。
CryptoBridge OpenLedger SparkDEX 给的教训还不够吗?还有 Deex 之流就不说了。

就算掰开手指数现在还在 BitShares 的公司机构,
也要先看 Move Institute , XBTS , ioBanker , 甚至 BEOS 。
什么时候轮得到 RuDEX ? RuDEX 根本都不是注册公司。

RuDEX 有关联开发团队不假。社区出钱开发的btspp手机钱包,他换个皮就是自己的了。申请一个 UI worker 拿了一百万多万没做完。后来又想申请 core worker 拿钱,我说你先提交点代码让我看看,结果没声了。回头变成我不放权?

你的聪明才智哪里去了?一个 Thule 天天在你耳边吹风,就只有他说的才是真话?
不说别的。他说锁喂价好你就支持锁喂价。 RuDEX 完全是反对锁喂价的,他有没有和你说?
他天天黑巨蟹你没听见过?还幻想巨蟹和他和RuDEX合作。
醒醒。

so many lies from you abit,
you are pitty


社区出钱开发的btspp手机钱包,他换个皮就是自己的了    这个不假吧!!!!!!!!!!!!!!!!!!!!!!    还能不承认?都知道的事情
Title: Re: [Witness Proposal] blckchnd
Post by: alt on October 03, 2020, 02:57:23 am
不知道你是真傻还是装傻,还在幻想你口中所谓的 business person 来拯救你。
CryptoBridge OpenLedger SparkDEX 给的教训还不够吗?还有 Deex 之流就不说了。

就算掰开手指数现在还在 BitShares 的公司机构,
也要先看 Move Institute , XBTS , ioBanker , 甚至 BEOS 。
什么时候轮得到 RuDEX ? RuDEX 根本都不是注册公司。

RuDEX 有关联开发团队不假。社区出钱开发的btspp手机钱包,他换个皮就是自己的了。申请一个 UI worker 拿了一百万多万没做完。后来又想申请 core worker 拿钱,我说你先提交点代码让我看看,结果没声了。回头变成我不放权?

你的聪明才智哪里去了?一个 Thule 天天在你耳边吹风,就只有他说的才是真话?
不说别的。他说锁喂价好你就支持锁喂价。 RuDEX 完全是反对锁喂价的,他有没有和你说?
他天天黑巨蟹你没听见过?还幻想巨蟹和他和RuDEX合作。
醒醒。

记得当初锁喂价是你提出的,怎么在你这变成thule了?
我代理给thule是因为社区里他思想比较开放,能听进各方的意见,也有自己的主见,即使他很多观念跟我不同我也从没威胁他迎合我。
解不解锁喂价都有道理,问题在于怎么执行。
市价跌破0.22,很多人爆仓单一直不主动调仓,在内盘规则为锁喂价的情况下,包括我在内的一些人,借出CNY,按0.22价格把爆仓单清了,你隔天马上解锁,号称要恢复锚定,反把这些仓位给爆了,这算什么事?
有人说不解锁对CNY持有人不公平。问题是CNY持有人在明知有锁喂价的情况下,在BTS市价高于0.22,有足够时间换人民币的情况下,仍然选择持有CNY,这难道不该自担风险?按规则0.22借CNY 的反而成老赖了?
解锁喂价没问题,但一定是在市价高于0.22的时候做,把影响降到最低,这点你能不清楚?

对smart coin, 很早我就说过自己的观点,不该强求锚定,重心要转为支持网关等业务,基于网关的DEX相对CEX是有足够的竞争资本的,在业务增加用户积累之后,smart coin自然会成长不断进步。
openledger 为什么离开我不清楚,社区有几个派别我也看不懂,很多时候是斗的你死我活,也不知道是为了什么,rudex一直在积极推动内盘市场,我当然支持,很多人对锁喂价有不同意见很正常,为什么不能给与理解。
巨蟹是陷到 smartcoin 精确锚定的牛角尖,可能也是因为这个和社区很多人关系紧张,回过头想想很不值得,可能是在舍本逐末。
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 03, 2020, 06:36:12 am
RuDEX 怎么赚钱的,我和你举个例子。
RuDEX 是上线了 STEEM 网关的。 STEEM 分叉空投 HIVE 的第一天,RuDEX 就把分到的 HIVE 转到交易所砸了。
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 03, 2020, 07:26:38 am
我代理给thule是因为社区里他思想比较开放,能听进各方的意见,也有自己的主见,即使他很多观念跟我不同我也从没威胁他迎合我。
他能听得进各方意见才见鬼了。
什么东西在他那里都成了阴谋论。
支持我的时候我做什么都是对的,不支持我的时候,什么错事都是我做的。
天天满口自己代表 majority community ,真不知道他怎么得出的结论。

他自己去年申请的worker说是到媒体发几篇宣传BTS的文章,钱拿了,到现在一篇都没发。

我本来也猜他不在乎一点小钱。
结果怎么?
公会上了一批自己的见证人,明摆着从系统搞钱,他和Dima巴巴的跟着上,把别人投下去,喂价也不喂,API节点也没跑,天天在群里、论坛上怼人。

公会搞新链时说好给他 500 万新币。当然,后来给没给、他要没要我不清楚。

Quote
解不解锁喂价都有道理,问题在于怎么执行。
市价跌破0.22,很多人爆仓单一直不主动调仓,在内盘规则为锁喂价的情况下,包括我在内的一些人,借出CNY,按0.22价格把爆仓单清了,你隔天马上解锁,号称要恢复锚定,反把这些仓位给爆了,这算什么事?
有人说不解锁对CNY持有人不公平。问题是CNY持有人在明知有锁喂价的情况下,在BTS市价高于0.22,有足够时间换人民币的情况下,仍然选择持有CNY,这难道不该自担风险?按规则0.22借CNY 的反而成老赖了?

解锁喂价没问题,但一定是在市价高于0.22的时候做,把影响降到最低,这点你能不清楚?
谁都知道我搞 4.0 是为了打破原有规则的。
你既然决定 0.22 救市,有什么风险你不清楚?
你现在选择止损不加抵押,我也理解。自担风险就是了。

锁喂价是我提的不假,我承认。但是,实际执行是因为你们的投票。
一开始可能还有点正面效果,有人津津乐道。
但看看后来执行成什么样子了?
从开始锁到现在,上过两次0.22了吧?持续时间也不短吧?解锁了吗?
内盘强清潮,曾经把所有抵押仓清到爆仓价 0.11 以下,即使解锁也没有爆仓风险,解锁了吗?

零和市场,规则变化,肯定有人受益有人受损。影响怎么算低怎么算高怎么判断?
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 03, 2020, 07:42:52 am
对smart coin, 很早我就说过自己的观点,不该强求锚定,重心要转为支持网关等业务,基于网关的DEX相对CEX是有足够的竞争资本的,在业务增加用户积累之后,smart coin自然会成长不断进步。
openledger 为什么离开我不清楚,社区有几个派别我也看不懂,很多时候是斗的你死我活,也不知道是为了什么,rudex一直在积极推动内盘市场,我当然支持,很多人对锁喂价有不同意见很正常,为什么不能给与理解。
巨蟹是陷到 smartcoin 精确锚定的牛角尖,可能也是因为这个和社区很多人关系紧张,回过头想想很不值得,可能是在舍本逐末。
支持网关业务是没错,我也知道。
但要网关自己也要努力,不能只想着从系统拿补贴,等人送到嘴里。
这方面 XBTS.io 做的相当不错,自己发展同时也宣传 BTS ,只是他们也还需要时间发展。
反观 RuDEX ,一边从 BTS 拿资源自己赚钱,一边回头踩 BTS 一脚。和 CryptoBridge 有的一比。

至于OL,你说你不清楚,你不会去问、去听、去看?连足额给用户提币都做不到,底线都没有,谈何发展?在群里的公开言论,说 BTS 只是一个免费试验场,要走私链路线。我只能说,道不同不相为谋。
Title: Re: [Witness Proposal] blckchnd
Post by: binggo on October 03, 2020, 08:58:20 am
支持网关业务是不错,但是不代表重点在于网关业务。

这些年这些网关业务带来的资金流还不如一个bitcny多,甚至于如果能够达到bitusd的水平都要烧香。

像AMM这样类型的DEX为什么能够火,因为它恰巧抓住了整个市场面的需求,我持有BTC能够生息吗?我持有USDT能够生息吗?我持有Eth可以生息吗?我持有其它代币可以生息吗?我又不想去承担抵押爆仓或者借贷暴雷的风险,现在有AMM恰巧提供给了市场这么一个可以存币提供流动性收获手续费,风险还小于抵押与借贷的机会,我又有什么理由不去试试?何况ETH上的生态圈还处于顶端。
它的前辈Bancor这么多年起来了吗,loopring起来了吗?一个跟eht关系这么密切的loopring都起不来,太过于奢求bts上的网关dex了。

网关DEX想要从这些CEX及AMM领头羊嘴里抢肉吃,就要比它们更灵活,更努力才行,热点能不能跟上?热点币能不能及时上?做市商能不能拉来?各种活动能不能做?热点功能BTS系统能够及时提供开发升级已经是最大的支持了,还要要求一条链为它上面的DAPP做什么呢?难道还要一条链把自己的开发资金拿出来给网关DEX做宣传做启动资金?何况网关DEX还存在致命性的信任问题!

各个网关应当是有独立的社群才能引流资金,而不是网关社群与bts社群重叠率高达90%,这样社区互割下去能持续多长时间?

我开发一个新功能,目的自然是需要吸引其它社区的资金与人员进来,持有btc的,持有eth的,持有其它的代币的来这里使用新功能,从而扩大用户面促进流动性。

一个makerdai可以靠抵押锚定资产发展到现在这个规模,bts难道不能够达到它一半的规模?这种系统自有业务的长足发展难道对系统的发展不更有裨益?
Makerdai最开始也是建了一个DEX,后来呢,不照样嗝屁掉了,最后还不是在抵押锚定规模上来了之后才重新开发设计了DEX,没有抵押锚定业务的稳定收入与长足发展,他们会有这个闲情去再开发一个dex?

一个锚定资产这么多年,被MSSR割,被强清割,被黑天鹅割,被喂价割,这四割的问题有哪一个被真正解决了?都想着社区互割不想着把整套抵押锚定的逻辑完完整整的捋顺,不认认真真的把整套机制设计完善,这怎么能够稳定发展开发?

票仓要么个个当甩手掌柜,要么迷迷糊糊,要么只顾贿选争权夺利,要么去搞其它链吸血,这搁到哪一条链上不嗝屁?
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 09:08:26 am


社区出钱开发的btspp手机钱包,他换个皮就是自己的了    这个不假吧!!!!!!!!!!!!!!!!!!!!!!    还能不承认?都知道的事情


It's just one more lie from scammer abit. We never said that it is our app, we localized for rudex users and gave the credits to their creators, this is an open source app, so I could do with the code as I please

(https://i.imgur.com/VWcHZ8s.png)

https://steemit.com/rudex/@rudex/rudex-mobile-app-announcement
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 09:11:43 am
RuDEX 怎么赚钱的,我和你举个例子。
RuDEX 是上线了 STEEM 网关的。 STEEM 分叉空投 HIVE 的第一天,RuDEX 就把分到的 HIVE 转到交易所砸了。

more lies from the abit

Read our user agreements.
For 4 years that we're operating on Bitshares, we never supported the forks.
So you trying now to make us look bad, but just shows how rotten you are
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 09:12:36 am
我代理给thule是因为社区里他思想比较开放,能听进各方的意见,也有自己的主见,即使他很多观念跟我不同我也从没威胁他迎合我。
他能听得进各方意见才见鬼了。
什么东西在他那里都成了阴谋论。
支持我的时候我做什么都是对的,不支持我的时候,什么错事都是我做的。
天天满口自己代表 majority community ,真不知道他怎么得出的结论。

他自己去年申请的worker说是到媒体发几篇宣传BTS的文章,钱拿了,到现在一篇都没发。

我本来也猜他不在乎一点小钱。
结果怎么?
公会上了一批自己的见证人,明摆着从系统搞钱,他和Dima巴巴的跟着上,把别人投下去,喂价也不喂,API节点也没跑,天天在群里、论坛上怼人。

公会搞新链时说好给他 500 万新币。当然,后来给没给、他要没要我不清楚。

Quote
解不解锁喂价都有道理,问题在于怎么执行。
市价跌破0.22,很多人爆仓单一直不主动调仓,在内盘规则为锁喂价的情况下,包括我在内的一些人,借出CNY,按0.22价格把爆仓单清了,你隔天马上解锁,号称要恢复锚定,反把这些仓位给爆了,这算什么事?
有人说不解锁对CNY持有人不公平。问题是CNY持有人在明知有锁喂价的情况下,在BTS市价高于0.22,有足够时间换人民币的情况下,仍然选择持有CNY,这难道不该自担风险?按规则0.22借CNY 的反而成老赖了?

解锁喂价没问题,但一定是在市价高于0.22的时候做,把影响降到最低,这点你能不清楚?
谁都知道我搞 4.0 是为了打破原有规则的。
你既然决定 0.22 救市,有什么风险你不清楚?
你现在选择止损不加抵押,我也理解。自担风险就是了。

锁喂价是我提的不假,我承认。但是,实际执行是因为你们的投票。
一开始可能还有点正面效果,有人津津乐道。
但看看后来执行成什么样子了?
从开始锁到现在,上过两次0.22了吧?持续时间也不短吧?解锁了吗?
内盘强清潮,曾经把所有抵押仓清到爆仓价 0.11 以下,即使解锁也没有爆仓风险,解锁了吗?

零和市场,规则变化,肯定有人受益有人受损。影响怎么算低怎么算高怎么判断?

more lies from a scammer abit

but because you banned Thule on these forum he can't answer to your false accusations,
he asked me to forward this on his behalf

Quote from: Thule

Abit you and Milos are manipulators notorious liars and fudders.


First of all the fud i received 5 million nbs for supporting came
from your mouth on bitsharesdac based on an article which cn-vote
posted.

I never asked for a single nbs from cn-vote.
I supported their witnesses before they even had a plan to fork out
of bitshares so your argument is just simple fud trying to discredit me
like you try everywhere but it seems not to be working.

Secondly i never received a single nbs other than airdrop on huobi.
So your attempt to make me look corrupt is just simple fud to make
your bad actions look better.


Even if cn-vote decided to give me 5 million nbs where i had no
interaction with it or even ever mentioned to get anything how could
you blame me for that ?


Other than you i never received a single token even you fudded it everywhere.
You on the other hand take money from the known scammer yip.



The next point about the articles.
I posted in feb i will use the the paid articles to promote the new
defi from bitshares which was in the core worker plan which was
delted thanks to you and milos.

You want me now to promote your dictatorship on bitshares and how
you destroy the whole ecosystem and reputation ?

I offered cn-vote after hearing that they have issues with cex'es
to update to the fork to restore old consensus to publish articles
describing the situation on bitshares to force cex'es to react.
Milos started to fud everywhere that cn-vote is making a hostile takeover
for which he even banned me officaly on this forum.
So you know exectly why cn-vote had issues on cex because you guys
told them lies that you made the changes based on consensus and cn-vote and me
are trying a hostile takeover.

CN-Vote stopped fighting for bitshares and decided to fork away
saying noone cares so they declined the offer.


About feed price threshold.
Abit like i said before you are a notorious liar.
Now you blame alt for it?
You know exectly you implemented the threshold
on your witness as first with no info,no bsip nothing.
Showed it to me and told it would be temporarly.
Since i wanted to safe big part of community beliving you it would be
only temporary i supported it which me and Dima disagreed heavily on telegram.
Today i can say it was a mistake because your word means nothing.
The temporarly changed to permanent even there was many times where
we could have fixed it without nearly any damage.
Remember my worker proposal to reduce feed price from 0.22 to 0.15
which would have caused no damage as lowest CR was 2.31 ?


You voted against it.
bitassets price was also higher than threshold.Where were you there?


old longterm bitsharians know your fud and know who created the mess and abused
his position for a long time.

How come you blame me only for not supporting you?

Was old core upset about your totalitarian behavior on github before ?
Was cn-vote and some other committee upset about your dictatorship in committee and MM before?
Was foreign community upset about your abuse in telegram ?
Was foreign community upset about the scammer workers you supported and defended before?
Was the community upset about your low ethics before?
I could make the list very long.
So claiming its just me seems you lost reality.

How did the foreign community called you abit before you even started mainnet 4.0 ?

A scammer and thief ?
Or is this conspiracy and fud from me ?


The next lie Abit wanting to protect users from abusers is just a
point to centralize bitshares.
OL,Sparkdex,CB were all registered companies.
How did it protected the users ?

On the other hand abits big supporters are

xbts
digital lucifer
beos
ammar


Someone just needs to listen to community what they think about them.

Is it a lie that digital lucifer tried activly to kick out gateways like
Rudex from bitshares ?
Calling them diffrent names ?
Is it a lie that Digital Lucifer tried to control all social media
accounts threatening to sue and acting like the owner of bitshares?
Is it a lie that Digital Lucifer acts like bitshares needs protection
as its been attacked everywhere and that he is going to provide protection
by being legal represantative and registering bitshares in thailand to have full control?


Sorry Abit i don't and won't support it.


Btw it's always a shady tactic to ban me and after that flood fuds about me where i can't even reply.
Like you guys did before
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 09:20:47 am
支持网关业务是没错,我也知道。
但要网关自己也要努力,不能只想着从系统拿补贴,等人送到嘴里。
这方面 XBTS.io 做的相当不错,自己发展同时也宣传 BTS ,只是他们也还需要时间发展。
反观 RuDEX ,一边从 BTS 拿资源自己赚钱,一边回头踩 BTS 一脚。和 CryptoBridge 有的一比。

至于OL,你说你不清楚,你不会去问、去听、去看?连足额给用户提币都做不到,底线都没有,谈何发展?在群里的公开言论,说 BTS 只是一个免费试验场,要走私链路线。我只能说,道不同不相为谋。

Рудекс на данный момент через арбитражных ботов делает ликвидность этому полумертвому чейну. Все остальные шлюзы с около нулевой ликвидностью, но они в отличие от нас лижут тебе жопу, а мы вертем тебя мудака на хую, поэтому тебя и бомбит еблан



RuDEX за четыре года своей работы не имел никаких проблем, даже при поддержке анонимной команды, в отличие от шлюзов со всеми бумажками, которые уже закрылись и ушли в закат со средствами пользователей.

Мы ЕДИНСТВЕННЫЙ шлюз Bitshares с полным аудитом: https://audit.rudex.org/

Этот аудит у нас достаточно давно, а все остальные шлюзы закрыли аудит, как только твой мошеннический MM конкурс закончился. Где аудит твоих шлюзов с бумажками?

Кстати по поводу ликвидности, просто для сравнения пошел, сделал несколько скринов минуту назад.

RuDEX
(https://i.imgur.com/DIh6zEb.png)

GDEX
(https://i.imgur.com/LSKjJpz.png)

XBTSX
(https://i.imgur.com/UJ4kaz5.png)

IObanker (honest_mpa)
(https://i.imgur.com/ezWTpFL.png)

Даже сейчас при полумертвой ликвидности на DEX, ликвидность RuDEX самая высокая

Мы как шлюз приносим этой платформе пользователей и комиссии, а ты abit только высасываешь эти комиссии через работников из общего пула. Совсем недавно ты обворовал сообщество получив деньги за аудит кода, в котором ты всех обманул и сломал консенсус. Ты вернул деньги за невыполненную работу обратно в пул?

abit ты лжец, вор и мошенник
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 03, 2020, 04:44:24 pm
不得不说 RuDEX 表面功夫做的还是不错的。所有的官宣里,没什么负面字眼。
进了群才知道实际是什么样。

至于 Thule ,转发一个群里的朋友的话,总结的很到位。
(https://user-images.githubusercontent.com/9946777/94996919-df5ca480-05a7-11eb-833b-31d320024709.png)
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 03, 2020, 05:07:14 pm
至于 Dima / blockchained / RuDEX , 其所作所为,下面老帖子你可以先围观一下。
如果要新的证据,我随时可以提供。

You just removed all messages from only 12 people. You can do better.

(https://user-images.githubusercontent.com/9946777/91200289-46608100-e6ff-11ea-9498-a9f4f7eeed28.png)
(https://user-images.githubusercontent.com/9946777/91200293-4791ae00-e6ff-11ea-85a8-8406de7e4fdc.png)
(https://user-images.githubusercontent.com/9946777/91200296-482a4480-e6ff-11ea-93e2-762dc1c7dad1.png)
(https://user-images.githubusercontent.com/9946777/91200297-48c2db00-e6ff-11ea-9721-ff5126105d06.png)
(https://user-images.githubusercontent.com/9946777/91200300-495b7180-e6ff-11ea-8a62-9e0c1da1fafd.png)
(https://user-images.githubusercontent.com/9946777/91200302-495b7180-e6ff-11ea-992c-bb2f55c14904.png)
(https://user-images.githubusercontent.com/9946777/91200306-49f40800-e6ff-11ea-97ad-a070011f9894.png)
(https://user-images.githubusercontent.com/9946777/91200309-4a8c9e80-e6ff-11ea-95ae-47ba1cdca3c5.png)
(https://user-images.githubusercontent.com/9946777/91200310-4b253500-e6ff-11ea-8739-c439714a05e3.png)
(https://user-images.githubusercontent.com/9946777/91200313-4b253500-e6ff-11ea-919f-4cdedb1e74b5.png)
(https://user-images.githubusercontent.com/9946777/91200315-4bbdcb80-e6ff-11ea-8e31-f26e22ba0475.png)
(https://user-images.githubusercontent.com/9946777/91200316-4c566200-e6ff-11ea-909e-0050a82ebcba.png)

当然,有同事支持。

Thanks to your friend Thule.

(https://user-images.githubusercontent.com/9946777/91193920-fdf19500-e6f7-11ea-9661-e41fb4601580.png)
(https://user-images.githubusercontent.com/9946777/91193917-fd58fe80-e6f7-11ea-8c2d-92b98cd11e93.png)
(https://user-images.githubusercontent.com/9946777/91193913-fc27d180-e6f7-11ea-9c99-de536506687d.png)

By the way,
(https://user-images.githubusercontent.com/9946777/91200830-f635ee80-e6ff-11ea-8644-27eea186b9ff.png)

Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 06:22:31 pm
至于 Dima / blockchained / RuDEX , 其所作所为,下面老帖子你可以先围观一下。
如果要新的证据,我随时可以提供。


А еще дима перебегал дорогу на красный свет.

Ты забыл добавить, что перед этим ты забанил своим ботом всех независимых админов и удалил все наши сообщения в чате
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 06:24:34 pm
不得不说 RuDEX 表面功夫做的还是不错的。所有的官宣里,没什么负面字眼。
进了群才知道实际是什么样。

至于 Thule ,转发一个群里的朋友的话,总结的很到位。

рынок решает, наша ликвидность и наш сервис как шлюза, это с чем мы работаем, а чат он для троллинга коррумпированных мудаков типа тебя abit, это не "поддержка шлюза"
Title: Re: [Witness Proposal] blckchnd
Post by: Ammar Yousef (ioBanker) on October 03, 2020, 06:48:04 pm
After abit trojan took place yesterday we've stopped our witness infrastructure for bitshares.

We have a capable team of core and UI devs, so we're preparing a fork of bitshares code base, back to the consensus rules that was before the abit abuse on github.
It will be a new distribution, a new chain, and a new genesis.
 
News will come latter with announcements.



We haven't seen your capable team of core and UI participating in any development related to BitShares as organization; your developments were obviously self-interests and private use cases ONLY; you were using the platform UI and the blockchain as a free database and application server for your CEX/Gateway use case; you never implemented new features nor fixed a single bug effecting BitShares.

There is no problem with utilizing BitShares as a free database and application server for CEX business use case; but BitShares isn't ONLY "CEX" business use case; we haven't seen any positive approach from your side nor a vision to support the ongoing development of BitShares; I had witnessed myself your FUD and attack on BitShares as if you were BitShares's competitor or enemy; spitting inside a plate that you were eating from in daily bases on Telegram with your team and supporters.

You were abusing your position as an admin on telegram, FUD, bad words and harassments; you were driving the masses to give up on BitShares while others were working on new features to change and to fix specific issues that was preventing the platform from growing.

Your failing strategy of attacking the network community, FUD, attacking developers and personalizing discussions isn't the strategy that is needed to change any facts on BitShares; BUT civilized discussions with community members which obviously you were lacking.

Some are really thinking BitShares is only a gateway/CEX application server and database engine; "CEX" decisions are self-interest naturally; BUT it isn't BitShares development. perhaps CEX voters are being paid back under the table by corrupt workers, WHY NOT; thanks to BitShares 5.0, this wouldn't be a case when voters are locking their BTS.

I believe you should stop acting as if you were important to BitShares Organization and I believe "alt" should rethink his mind about you.

Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 03, 2020, 07:09:07 pm
We haven't seen

Who are we?
You are banker from the barn, with a law liquidity gateway, fanboy of Milos and Abit, go work on your liquidity 

Because RuDEX still here and even without shithole registration in Estonia our liquidity higher

There is no we, you represent just your big mouth
Don't bla bla bla, banker from the barn better work on your liquidity

I had witnessed myself
Words from the mouth of the dev with low ethics is worthless
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 03, 2020, 07:34:50 pm

公会搞新链时说好给他 500 万新币。当然,后来给没给、他要没要我不清楚。

有人建议我把这事澄清一下。

可能公会确实(还)没给他币。
公会的信用,怎么说呢,空投当天改空投规则的事也是实实在在发生了的。
公会以后会怎么做,谁也不清楚。
特别是,为了打我的脸,就不给他了,也正常。

这个500万具体是什么事情呢?
公会的正式公告 https://btsgh.com/?p=365 里有了一句“公会合作盟友将获得 500 万 NBS 的奖励”,没有明说给谁,很巧妙是吧。
但我看过一个草稿,里面写的是“公会合作盟友bdex将获得 500 万 NBS ”。
信不信由你。

至于为什么这位是公会合作盟友?因为 4.0 版本生效后这位盟友拿着你 alt 代理的票,和公会一起,投上了一大批试图分叉、其他什么贡献都没有的见证人(包括星在飘都跑了好几个见证人,后来他的主马甲 baidu 被揪出来了后有没有换新马甲我不清楚)。

(https://user-images.githubusercontent.com/9946777/89977753-3a3ee300-dc6c-11ea-8463-e2a62030e51c.png)


再说一句,我为什么说公会试图在8月20号制造分叉(针对有人一直纠结于说公会并不想分叉)。
因为实际上这是个技术事实 —— 不同见证人运行不同版本、互不兼容的节点,就会出现分叉。
(我个人并不反对有实力的团队进行分叉,只要能保证原链稳定运行)。

看看这个通知 https://bitsharestalk.org/index.php?topic=32560.0
威胁所有见证人在 8月20号前运行公会的“补丁”版本,不运行就撤票,没有足够人支持就自己跑见证人,这不是分叉是什么?后来也确实这么做了,撤了一批人,新上了一批人。只是最后关头,这些上去的见证人还是跑了原版代码。
我就奇怪了,既然还是跑原版代码,搞这么大声势干什么?
新上的见证人,除了要分一部分工资给公会上贡,对社区、对系统做了什么贡献?占着位置,甚至连个喂价都喂不好。哦,有些人根本就没喂。反正有票,管他呢。
Title: Re: [Witness Proposal] blckchnd
Post by: alt on October 03, 2020, 10:37:18 pm
seems it's off topic far away,
I'm not interested in those gossip.
I can see rudex's effort from the order book in the past weeks,
Wish rudex could stay with Bitshares.
Title: Re: [Witness Proposal] blckchnd
Post by: xixi002020 on October 04, 2020, 01:51:31 am
seems it's off topic far away,
I'm not interested in those gossip.
I can see rudex's effort from the order book in the past weeks,
Wish rudex could stay with Bitshares.

是有这么回事,不是流言蜚语,不信你完全不知情,为虎作伥罢了。
锁喂价确实是abit提出来的,只是是临时提出的,锁多久,什么时候解锁,等等...都没有,没有完整的方案。 这一点abit是有责任的。
当然以前的投票机制 即使有完整方案  能不能正常执行另说.............
Title: Re: [Witness Proposal] blckchnd
Post by: Ammar Yousef (ioBanker) on October 04, 2020, 05:23:43 am
seems it's off topic far away,
I'm not interested in those gossip.
I can see rudex's effort from the order book in the past weeks,
Wish rudex could stay with Bitshares.

He will stay don't worry; he cannot trust NBS airport to run his free database and application server.

His CEX orderbook is not even 1% of daily volume https://coinmarketcap.com/currencies/bitshares/markets and his harassments to BitShares community wouldn't be justified nor forgiven.
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 04, 2020, 07:13:51 am
seems it's off topic far away,
I'm not interested in those gossip.
I can see rudex's effort from the order book in the past weeks,
Wish rudex could stay with Bitshares.
It's not gossip but public info.
You're free to choose to ignore them anyway, it is called "Selective blindness" (选择性失明).
Wish you good luck.
Title: Re: [Witness Proposal] blckchnd
Post by: alt on October 04, 2020, 08:41:08 am
是不是太自以为是了,怎么和你关注点不同就是选择性失明了
同一个事情,你觉得自己是BTS救星,铁腕改革,我看你是玩过家家胡闹,谁看谁都是失明的。


seems it's off topic far away,
I'm not interested in those gossip.
I can see rudex's effort from the order book in the past weeks,
Wish rudex could stay with Bitshares.
It's not gossip but public info.
You're free to choose to ignore them anyway, it is called "Selective blindness" (选择性失明).
Wish you good luck.
Title: Re: [Witness Proposal] blckchnd
Post by: abit on October 04, 2020, 08:55:11 am
是不是太自以为是了,怎么和你关注点不同就是选择性失明了
同一个事情,你觉得自己是BTS救星,铁腕改革,我看你是玩过家家胡闹,谁看谁都是失明的。


seems it's off topic far away,
I'm not interested in those gossip.
I can see rudex's effort from the order book in the past weeks,
Wish rudex could stay with Bitshares.
It's not gossip but public info.
You're free to choose to ignore them anyway, it is called "Selective blindness" (选择性失明).
Wish you good luck.
话已至此,不必多说。
你行你上。
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 04, 2020, 09:51:08 am
All further RuDEX announcements will be published in our official channels:

https://steemit.com/@rudex
https://golos.id/@rudex
https://twitter.com/team_rudex
https://t.me/RU_DEX


Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 04, 2020, 09:57:47 am
It's not gossip but public info.

It's just your FUD abit, your started it first in a chat to discredit Thule, you have no proof besides your rotten word

And btw if you attack our anonymity open your face first, do it please, I really want to know who you are. How dare you attack anyone anonymity meanwhile destroying this project from anonymous nickname by yourself?
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 04, 2020, 10:06:48 am
I agree all these things are ridiculous.
I think it's not a big deal to change to another official github address if we have enough vote power.

I tend to agree it is the only way to save this project is to change official github. To protect existing and future businesses from one man dictatorship that happens now.
Also, it would be good move to change "official" dns to bitshares.exchange from bitshares.org.
We have at least 2 reason to support this
1) .org dns belongs to Milos that numerous times threat our gateway, and he has plan to filter it,

(https://i.imgur.com/ODB1bhE.png)

also he was manager of the core that brought trojan in the 4.0 release, and he publicly supported broke of consensus

(https://i.imgur.com/2FdhBxq.png)

2) bitshares.exchange the dns name that was bought by the community and belong to the community, so the community already spent money to obtain it, and now the correct time to use it
Title: Re: [Witness Proposal] blckchnd
Post by: alt on October 04, 2020, 11:11:11 am
I agree this could be a security threat, and your advice is a possible choice, we can make a comunity consensus by voting.

I agree all these things are ridiculous.
I think it's not a big deal to change to another official github address if we have enough vote power.

I tend to agree it is the only way to save this project is to change official github. To protect existing and future businesses from one man dictatorship that happens now.
Also, it would be good move to change "official" dns to bitshares.exchange from bitshares.org.
We have at least 2 reason to support this
1) .org dns belongs to Milos that numerous times threat our gateway, and he has plan to filter it,

(https://i.imgur.com/ODB1bhE.png)

also he was manager of the core that brought trojan in the 4.0 release, and he publicly supported broke of consensus

(https://i.imgur.com/2FdhBxq.png)

2) bitshares.exchange the dns name that was bought by the community and belong to the community, so the community already spent money to obtain it, and now the correct time to use it
Title: Re: [Witness Proposal] blckchnd
Post by: Ammar Yousef (ioBanker) on October 04, 2020, 12:09:08 pm
His CEX orderbook is not even 1% of daily volume coinmarketcap
Your CEX iobanker is even not on cmc, boy

ioBanker isn't CEX nor a gateway; stop comparing your poor startup with ioBanker, kid.
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on October 04, 2020, 12:22:31 pm
All further RuDEX announcements will be published in our official channels:

https://steemit.com/@rudex
https://golos.id/@rudex
https://twitter.com/team_rudex
https://t.me/RU_DEX


Title: Re: [Witness Proposal] blckchnd
Post by: binggo on October 04, 2020, 01:14:49 pm
这真TM算是币圈一景啊, 个个嘴上都喊着维护共识,心里却想的是镰刀,前有无限正义的珠玉cn-vote,我想后必有更加无限正义的***

真是个个都想回到“狡伪成风,吏民相沿,不以为非”的时候。

Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on November 12, 2020, 09:30:33 pm
After abit trojan took place yesterday we've stopped our witness infrastructure for bitshares.

We have a capable team of core and UI devs, so we're preparing a fork of bitshares code base, back to the consensus rules that was before the abit abuse on github.
It will be a new distribution, a new chain, and a new genesis.
 
News will come latter with announcements.

Hello everyone!

Those of you who are following the Bitshares platform certainly know about the recent event, that caused a lot of debate. During the BTS4.0 protocol upgrade, one of the hired core devs (abitmore) added a community unapproved backdoor to the code, which led to the change of the voting rights, and a major change of the consensus procedure. As a result multiple conflicts ensued with a significant portion of chinese community leaving Bitshares.

After thoroughly analysing the consensus changes, that were made without voting or any discussion by community members, we verified that the resulting system is unscalable and doomed to stagnate. As a result our team decided to launch a fork of stable and time tested Bitshares3.0 consensus code using Graphene — the original name of the technology.

Graphene (https://www.gph.ai) is the industrial grade technology, adapted both for private and company use. For years it was a foundation for the unique ecosystem and market economy. Its open source code and MIT license allow for creation and maintenance of different decentralized blockchain applications with workers system, that allows core token holders to elect which development to support.

To avoid the mistakes that resulted in the current status quo in Bitshares, we’ve reduced the maximum supply of GPH tokens, and decided to hold the initial distribution of Graphene (https://www.gph.ai) tokens via all win and provably fair lottery.
The lottery would distribute 40 out of 100 million tokens, with further 60 million used in the reserve fund. The distributed tokens will form the genesis block of the Graphene blockchain, and all undistributed tokens from the 40 million will be burned.
Final supply will be formed out of the resulting sum (reserve fund + distributed tokens); 6% of that supply will be vested to the launch team with the following ratio: 1% will become available to the team within the first week of the launch, and the remaining 5% will be vested over the next 10 years.


GPH token has a limited supply, which differs from the liquid circulating supply. 60 million tokens are set aside for financing projects and block producer rewards. These funds will be available to the worker system only from GPH token holders approval. This working budget is known as “reserve pool”.
It is worth mentioning that transaction fees are not distributed among the GPH token holders, but are returned to the worker budget to pay for further development. There is no reward for holding the GPH core token in your wallet.

## About lottery

The lottery starts on the RuDEX platform concurrently with the publication of this announcement and will last for 40 days. Every days only 100,000 lottery tickets will be available, and with the end of the lottery period all undistributed tokens will be burned, with the final supply and genesis block of the new blockchain being formed as the result.

To participate in the lottery, you will have to buy a lotto (https://market.rudex.org/#/market/RUDEX.LOTTERY_RUDEX.BTC) ticket and register (https://market.rudex.org/#/lottery) it.

Every registered ticket will allow you to win from 1 to 30 GPH tokens. For ease and transparency the lottery will be held on the Bitshares blockchain.

There are only 5 possible winning combinations with a fixed amount of tokens for each combination, as follows:

0 - 1
1 - 3
2 - 6
3 - 10
4 - 30

The combination number (0-4) will be calculated from the transaction hash on the ticket registration.

To demonstrate how the lottery works we will use RUDEX.LOTTERY token as an example.
As you can see in this block https://bts.ai/block/53159405 bot-11 account “registered” 1 RUDEX.LOTTERY and got a transaction number TXID of d60c7ce9467043cf81acd5fdb1c5bc851d20faed.
If this value is divided by modulo 5 (number of combinations), then the remainder of the division will be the combination number of this ticket. You can verify the division remainder using, for example, the following service: https://defuse.ca/big-number-calculator.htm
In our case you need to insert the following line into the calculator 0xd60c7ce9467043cf81acd5fdb1c5bc851d20faed  % 5, which is equal to the value of 4, which is a combination for 30 GPH token win.

It is possible to register any number of tickets concurrently, which results in cycles of combinations (0-4) are counted from the division reminder value of the transaction hash until all tickets are given the result.

For your ease and convenience the lottery page display the transaction hashes and results for all of your registered tickets. Every lottery result is available for a public review.

So if you are as tired of the unfair games and underhanded intrigues as we are, we are inviting you to start anew and open the Graphene technology in its original balanced and transparent nature

https://market.rudex.org/#/lottery

Title: Re: [Witness Proposal] blckchnd
Post by: abit on November 13, 2020, 06:49:07 am
Effectively you are doing an ICO capped at 5 BTC per day if the price for each ticket won't change. The total fund to raise is 5*40 = 200 BTC.

Quote
As you can see in this block https://bts.ai/block/53159405 bot-11 account “registered” 1 RUDEX.LOTTERY and got a transaction number TXID of d60c7ce9467043cf81acd5fdb1c5bc851d20faed.
If this value is divided by modulo 5 (number of combinations), then the remainder of the division will be the combination number of this ticket. You can verify the division remainder using, for example, the following service: https://defuse.ca/big-number-calculator.htm
In our case you need to insert the following line into the calculator 0xd60c7ce9467043cf81acd5fdb1c5bc851d20faed  % 5, which is equal to the value of 4, which is a combination for 30 GPH token win.
Just for the info:

It is very simple for a skilled programmer to "mine" (brute force) the TXID and only submit the transaction to the blockchain if 4 is the remainder, with no extra cost.

Guess how many times you need to try to get your desired value if the chance is 20% every time. It is 5 times on average.

IMHO the design is stupid.

Good luck anyway.

Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on November 13, 2020, 10:33:16 am
All further RuDEX announcements will be published in our official channels:

https://steemit.com/@rudex
https://golos.id/@rudex
https://twitter.com/team_rudex
https://t.me/RU_DEX


---

Those of you who are following the Bitshares platform certainly know about the recent event, that caused a lot of debate. During the BTS4.0 protocol upgrade, one of the hired core devs (abitmore) added a community unapproved backdoor to the code, which led to the change of the voting rights, and a major change of the consensus procedure. As a result multiple conflicts ensued with a significant portion of chinese community leaving Bitshares.

After thoroughly analysing the consensus changes, that were made without voting or any discussion by community members, we verified that the resulting system is unscalable and doomed to stagnate. As a result our team decided to launch a fork of stable and time tested Bitshares3.0 consensus code using Graphene — the original name of the technology.


---
Title: Re: [Witness Proposal] blckchnd
Post by: Ammar Yousef (ioBanker) on November 13, 2020, 05:37:57 pm
After abit trojan took place yesterday we've stopped our witness infrastructure for bitshares.

We have a capable team of core and UI devs, so we're preparing a fork of bitshares code base, back to the consensus rules that was before the abit abuse on github.
It will be a new distribution, a new chain, and a new genesis.
 
News will come latter with announcements.

Hello everyone!

Those of you who are following the Bitshares platform certainly know about the recent event, that caused a lot of debate. During the BTS4.0 protocol upgrade, one of the hired core devs (abitmore) added a community unapproved backdoor to the code, which led to the change of the voting rights, and a major change of the consensus procedure. As a result multiple conflicts ensued with a significant portion of chinese community leaving Bitshares.

After thoroughly analysing the consensus changes, that were made without voting or any discussion by community members, we verified that the resulting system is unscalable and doomed to stagnate. As a result our team decided to launch a fork of stable and time tested Bitshares3.0 consensus code using Graphene — the original name of the technology.

Graphene (https://www.gph.ai) is the industrial grade technology, adapted both for private and company use. For years it was a foundation for the unique ecosystem and market economy. Its open source code and MIT license allow for creation and maintenance of different decentralized blockchain applications with workers system, that allows core token holders to elect which development to support.

To avoid the mistakes that resulted in the current status quo in Bitshares, we’ve reduced the maximum supply of GPH tokens, and decided to hold the initial distribution of Graphene (https://www.gph.ai) tokens via all win and provably fair lottery.
The lottery would distribute 40 out of 100 million tokens, with further 60 million used in the reserve fund. The distributed tokens will form the genesis block of the Graphene blockchain, and all undistributed tokens from the 40 million will be burned.
Final supply will be formed out of the resulting sum (reserve fund + distributed tokens); 6% of that supply will be vested to the launch team with the following ratio: 1% will become available to the team within the first week of the launch, and the remaining 5% will be vested over the next 10 years.


GPH token has a limited supply, which differs from the liquid circulating supply. 60 million tokens are set aside for financing projects and block producer rewards. These funds will be available to the worker system only from GPH token holders approval. This working budget is known as “reserve pool”.
It is worth mentioning that transaction fees are not distributed among the GPH token holders, but are returned to the worker budget to pay for further development. There is no reward for holding the GPH core token in your wallet.

## About lottery

The lottery starts on the RuDEX platform concurrently with the publication of this announcement and will last for 40 days. Every days only 100,000 lottery tickets will be available, and with the end of the lottery period all undistributed tokens will be burned, with the final supply and genesis block of the new blockchain being formed as the result.

To participate in the lottery, you will have to buy a lotto (https://market.rudex.org/#/market/RUDEX.LOTTERY_RUDEX.BTC) ticket and register (https://market.rudex.org/#/lottery) it.

Every registered ticket will allow you to win from 1 to 30 GPH tokens. For ease and transparency the lottery will be held on the Bitshares blockchain.

There are only 5 possible winning combinations with a fixed amount of tokens for each combination, as follows:

0 - 1
1 - 3
2 - 6
3 - 10
4 - 30

The combination number (0-4) will be calculated from the transaction hash on the ticket registration.

To demonstrate how the lottery works we will use RUDEX.LOTTERY token as an example.
As you can see in this block https://bts.ai/block/53159405 bot-11 account “registered” 1 RUDEX.LOTTERY and got a transaction number TXID of d60c7ce9467043cf81acd5fdb1c5bc851d20faed.
If this value is divided by modulo 5 (number of combinations), then the remainder of the division will be the combination number of this ticket. You can verify the division remainder using, for example, the following service: https://defuse.ca/big-number-calculator.htm
In our case you need to insert the following line into the calculator 0xd60c7ce9467043cf81acd5fdb1c5bc851d20faed  % 5, which is equal to the value of 4, which is a combination for 30 GPH token win.

It is possible to register any number of tickets concurrently, which results in cycles of combinations (0-4) are counted from the division reminder value of the transaction hash until all tickets are given the result.

For your ease and convenience the lottery page display the transaction hashes and results for all of your registered tickets. Every lottery result is available for a public review.

So if you are as tired of the unfair games and underhanded intrigues as we are, we are inviting you to start anew and open the Graphene technology in its original balanced and transparent nature

https://market.rudex.org/#/lottery

Your opinion about BitShares isn't credited; I don't see your initial distribution making any sense, I suggest you do some MLM schemes like selling replica watches for your GPH so it might have value.
Title: Re: [Witness Proposal] blckchnd
Post by: blockchained on November 13, 2020, 07:13:21 pm
All further RuDEX announcements will be published in our official channels:

https://steemit.com/@rudex
https://golos.id/@rudex
https://twitter.com/team_rudex
https://t.me/RU_DEX


---

Those of you who are following the Bitshares platform certainly know about the recent event, that caused a lot of debate. During the BTS4.0 protocol upgrade, one of the hired core devs (abitmore) added a community unapproved backdoor to the code, which led to the change of the voting rights, and a major change of the consensus procedure. As a result multiple conflicts ensued with a significant portion of chinese community leaving Bitshares.

After thoroughly analysing the consensus changes, that were made without voting or any discussion by community members, we verified that the resulting system is unscalable and doomed to stagnate. As a result our team decided to launch a fork of stable and time tested Bitshares3.0 consensus code using Graphene — the original name of the technology.

---

Bitshares Drama

This is a translation, Russian original: https://golos.id/ru--blokcheijn/@akledirs/khroniki-dramy-v-bitshares

There always is, was and will be a place for drama in Bitshares, as it is a blockchain with DPoS DPoBS consensus, where “meat bags” play an important role. In the last year the scale of the drama reached mythica sizes. Recently in Russian community there was a request for coverage of the events that split the community and resulted in the launch of two new blockchains. This request was answered by Alexey Petrov (@tnam0rken) with his article “Split in the Bitshares community. How it happened…” (https://golos.id/ru--blokcheijn/@tnam0rken/raskol-v-soobshestve-bitshares-kak-eto-bylo) (article is in Russian)

Below is my attempt to cover some facts and events during this period in more detail, gather all the scattered pieces of information and all the changes that affected the chain of events. I am doing this for all who are interested in the history of the project, and would like to understand these events better. Some of the details that were covered by Alexey’s article will be omitted here for the sake of brevity.

HF 4.0

30 June 2020 a new version of Bitshares-core was released (https://github.com/bitshares/bitshares-core/releases/tag/4.0.0), which included a significant upgrade of the protocol (hardfork) to version 4.0. Release was planned for November 2019, but due to changes in votes for the core worker and disruption in financing that resulted the release was delayed.

Protocol activation happens with a delay of 1 month, which means that the changes will come into effect on 30 July 2020. To get details about the changes in the release you can check the release page (https://github.com/bitshares/bitshares-core/releases/tag/4.0.0). Here I will list the most significant.

Economic model changes


BSIP-74 (https://github.com/bitshares/bsips/blob/master/bsip-0074.md) — Introduction of a Margin Call Fee Ratio
In addition to the Maximum Short Squeeze Ration (MSSR), which is the premium that goes from the borrower that allowed a margin call to happen to MPA holder that sells their assets to fill that call, an additional fee is introduced, that can be set by the asset owner, and that is paid by the borrower — Margin Call Fee Ration (MCFR).

Info about this fee is not displayed in the UI.

BSIP-75 (https://github.com/bitshares/bsips/blob/master/bsip-0075.md) — Asset Owner Defines MCR and MSSR Values
Now the owner of the asset can define who can change those parameters (asset owner or blockchain witnesses, before the change only witnesses could change them). Additionally the owner can freeze the values, and permanently decline the access to change it, which results in lower control over the smartasset, but higher level of trust, that results from the lowering of the amount of vectors for manipulation.

BSIP-77 (https://github.com/bitshares/bsips/blob/master/bsip-0077.md) — Require Higher CR When Creating / Adjusting Debt Positions
A new parameter is added to all MPAs — Initial Collateral Ration (ICR), that is defined by the smart asset owner or witnesses. It allows the blockchain to require from the borrower to put up higher collateral in relation to the Maintenance Collateral Ration (MCR).

BSIP-81 (https://github.com/bitshares/bsips/blob/master/bsip-0081.md)— Simple Maker-Taker Market Fees
Now the asset owner can define different market fees for the asset buyer, depending on whether the order is filled from the market (Taker), or is added to the order book (Maker). By default the fees are equal.

UI does not reflect the difference in the fees.

BSIP-85 (https://github.com/bitshares/bsips/blob/master/bsip-0085.md) — Maker order creation fee discount
In essence this proposal is similar to BSIP-81, but in this case it talks about fees in BTS and their size is defined by the blockchain committee.

BSIP-86  (https://github.com/bitshares/bsips/blob/master/bsip-0086.md)— Share market fees to the network
This inconspicuous name hides a tax on the revenue of the asset owner from the market fees. Committee can now set a ratio of up to 30% that the asset owner must pay to the committee account vesting balance. The idea to call things as they are and rename the BSIP to “Share market fees to the committee” got a negative reaction from Abit (https://github.com/bitshares/bsips/pull/270#issuecomment-616542051).

BSIP-87 (https://github.com/bitshares/bsips/blob/master/bsip-0087.md) — Force Settlement Fee
In addition to static MPA Force Settlement fee and Force Settlement Offset (FSO), that is paid by the user requesting the settlement to the borrower, this BSIP adds an ability to specify a percentage fee from the amount of amount being settled (Force Settlement Fee Percentage (FSFP)). The size of the fee is set by the asset owner and is paid from the user requesting Force Settlement to the asset owner when the MPA is settled. The change was suggested by bitcrab (Jerry Lee) and supported by Abit.

This adds a new risk for smartcoin holders: the asset owner can at any point specify a 100% fee, in effect taking the collateral without an ability to control it until the settlement request. The risk is made more severe by the fact that the information about the fee amount is not displayed in UI.

Governance model changes

These changes were not announced — they were added by the auditor (abit) despite no consensus decision on them. These changes were announced after (https://bitsharestalk.org/index.php?topic=32546.0) the fact.

BTS in collateral are no longer counted for voting purposes.

Why was this decision made? Let us use Abit’s explanation:

The past flaw was simply that BTS in locked collateral would retain voting power. So when those holders found the market against them, were easily corrupted to vote against the common good. In other words, give everyone a free vote, and a majority will always form to use it for ‘themselves’.

The result of a group of holders doubling power through collateral, then locking price feeds through block producers, held the blockchain ‘hostage’ since 2019 – destroying the standing reputation of a product with highest demand in 2020.

BitShares BitAssets Reloaded | Committee Owned True StableCoins (https://news.bitshares.org/bitshares-reloaded-bitassets1/)

Indeed a group of borrowers, who were also holders of BTS, used collateralized borrowing to increase their stake in the project to a significant level. They had an interest to protect their capital, influence and also enough influence to elect witnesses who would provide feeds that would satisfy their interest. And they used that tactics for a long time to provide fake feeds, promote BSIP-42 (https://github.com/bitshares/bsips/blob/master/bsip-0042.md) and price feed level freeze (https://bitsharestalk.org/index.php?topic=27753.0) at a set level for bitUSD and bitCNY. A conflict of interest is apparent, and talks about it were ongoing since 2018. Something had to change, but the borrowers facing margin call liquidations of all of their leveraged positions were clearly against it.

Automatic vote weight decrease for sleeping accounts
After each vote the vote weight would return to 100%. First 360 days of inactivity it is lowered by 12.5%, and then for 315 day the weight is decreased by additional 12.5% points every 45 days. On day 675 of inactivity the vote weight is 0.

One vote principle
If the holder of BTS votes for more than one committee member, then the sum of their stake weight is split among the number of votes for committee members. Before the change every voted member would receive full stake weight of the voter.

Staking based voting
This change requires freezing BTS for them to be eligible for voting with 4 durations: 180/360/720/∞ days. Depending on selected duration a multiplier of x2/x4/x8/x0 is applied respectively. x0 multiplier for permanent freeze is explained below. Fee for this transaction type is 50 BTS and not subject to change by committee.

In the case of the permanent blocking of BTS the blocked amount loses its vote weight and can not be used ever, which is equal to burning of BTS, but the equivalent sum staked has a multiplier of x8 applied to it. The multiplier is temporary, it decreases every 180 days by half, and in 720 days its influence is over. The maximum multiplier possible using the staking rules is capped at x32.

After the staking transaction the multiplier comes into effect gradually in stages, with a delay after every stage, each stage comes into effect in 15 more days. The staking can be canceled in 15 days, but tokens will stay staked for 7 more days.

Unstaking transaction removes the multiplier immediately, but the funds will stay staked for the period chosen by the user during staking. In case of the permanent token lock, the funds will stay blocked.

A user can have more than one staked position, with duration of the staked positions tracked separately.

After the first permanent staked position...

New rules come into the effect:

- Accounts that do not have at least 1 BTS staked do not participate in the voting;
- BTS used as an MPA collateral no longer have voting power;
- BTS in the order books no longer have voting power.

DPoBS — new consensus algorithm and its justification
This new model where voting preference is given to those who stake, and even effectively burn their tokens by permanently blocking them, which results in deflation Abit has called (https://bitsharestalk.org/index.php?topic=32357.0) DPoBS — Delegated Proof of Burn and Proof of Stake

CustomMiner has suggested (https://github.com/bitshares/bsips/blob/master/bsip-0024.md) back in 2017 the implementation of BSIP-0024 that gives voting preference for those who stake their BTS.

You can get the most detailed view on Abit’s stance on voting by reading this article on Github from 2018 New BSIP or BSIP24 discussion: stake lock-up mechanism, count only real "locked" stake as voting stake (https://github.com/bitshares/bsips/issues/83) .

On 30th July 2020 the hardfork with all the changes described above has come into effect. A curious fix (https://github.com/bitshares/bitshares-core/issues/2103) was also added, that corrected the displayed maximum supply of Bitshares. The actual supply was higher by 250 million coins higher, than any of the blockchain explorers showed, including what was displayed on Coinmarketcap.

CNVOTE reaction -> New Bitshares

On 31st of July first people who noticed the non standard behavior of the voting page, and some committee members started asking questions about the changes to the voting model to the developers. As a result it was discovered who was behind those non consensus changes, and votes were removed from Abit.
On 2nd of August the CNVOTE team started developing a fix that would affirm the existing consensus from before the hardfork. During the fix development a heated debate was happening, with defenders of abit’s changes arguing that there is some value to the changes, and since it happened it would be better not to change anything.
By 10th of August the fix was ready, but to deploy it CNVOTE needed to convince the witnesses to apply it, which encountered some difficulties.
On 16th of August Abit was approached with a request to relinquish the control over the official Github repository to committee, but he declined
On 17th of August after deciding that further effort in applying the patch is hopeless the CNVOTE team decided to create a new blockchain BTS4.0 upgrade tampering code incident | NewBitshares [CN] (http://news.newbitshares.org/?p=218)
Announcement on Implementation of BTS CNVOTE Patch | BitsharesTalk [CN, EN] (https://bitsharestalk.org/index.php?topic=32584.0)
On 30th of August 2020 the chinese community unhappy with the changes and coming transition to a harsher voting model announces (https://bitcointalk.org/index.php?topic=5272354) a new blockchain based on BTS 4.0 code, but without changes to the voting model added by Abit. Many call this a fork, but only the codebase was forked with the blockchain formed from a new genesis.
On 10th of September the network was launched named NewBitshares, and the token with NBS ticker.
Next Hardfork — Splash (5.x)

On 22nd of September a new Bitshares core was released (https://github.com/bitshares/bitshares-core/releases/tag/5.0.0), with the hardfork planned for 28th of September.

This hardfork included two main changes — the support for AMM liquidity pools, and another change to the governance model — now unstaked BTS do not have any voting weight at all.

On the next day everything came tumbling down. Abit consolidates the control over the network by staking his funds. Due to effectively sole control over the network he elects loyal witnesses and committee members. The committee (aka Abit) disables MPA borrowing (block 51860407) (https://bitsharestalk.org/index.php?topic=32640.0) for bitCNY and bitUSD, the blockreward for witnesses is lowered to 0.1 BTS, and order placement fee is raised 20 times, MSSR for bitUSD is raised to 1.1, which results in the global settlement for bitUSD (block 51889804) (https://bitsharestalk.org/index.php?topic=32646.0). Here we need to remind you, that fake oracle feeds were in effect which were against the borrowers of bitUSD. As a result bitUSD holders could get less than 70% of the tokens used as a collateral going by the spot prices at that time. bitCNY situation was similar, but Abit decided against doing the same there.

In addition now the committee decides who can provide bitasset feeds. Witnesses can not provide feeds without committee approval.

As a result of those news XCHNG announces closing of their Tre-Fund (market ticker XCHNG.FUND).


On the same day a batch of new bitassets is created by committee — bitassets 1.0. By the announcement of the committee the MSSR, MCR, delay and force settlement price offset will not be changed in the future [BitsharesTalk] (https://bitsharestalk.org/index.php?topic=32647.0)[News Bitshares] (https://news.bitshares.org/bitshares-reloaded-bitassets1/).

RuDEX/BLCKCHND reaction -> Graphene


Blckchnd witness has publicly denounced Abit’s actions everywhere they could, and as a result was banned in the main english BitsharesDAC chat.
Team RuDEX supported CNVOTE fix patch
On 16th of September RuDEX launched an NBS gateway (https://steemit.com/rudex/@rudex/newbitshares-nbs-gateway-on-decentralized-trading-platform-bitshares-rudex-launched) on bitshares, as well as a public access point (https://market.nbsdex.io/) for the new network.
On 29th of September in the RUDEX Trollbox chat Dima BLCKCHND (@blockchained) announced a fork based on BTS 3.0 codebase named Graphene
On 12th of November 2020 team RuDEX announced (https://steemit.com/blockchain/@rudex/graphene-blockchain-by-rudex-team-initial-distribution-announcement) an all win lottery to get the initial distribution and form a genesis block for the new chain
On 23rd of December the results of the lottery (https://steemit.com/graphene/@rudex/graphene-lottery-end-announcement) were published, and all participants were given a stake and their funds were returned, possibly as a result of my critical comments on the lottery mechanics

On 12th of April 2021 a new chain was launched (https://gph.ai/) with GPH token ticker, and the maximum supply of 100 million tokens.
UPD
- On 27th of May 2021 RuDEX have migrated (https://steemit.com/rudex/@rudex/announcement-of-rudex-migration-from-bitshares-to-graphene-dates-and-terms) to Graphene from Bitshares.

And now you are here...

On 19th of May the private Honest.USD smartcoin honestly went into global settlement state. In the next 24 hours ⅔ of all coins in circulation during the black swan event were settled. Such a significant reduction in debt, small volume and price bounce allowed @Chibchombia (BTS: imm-ortal) to revive the asset on the very next day.

On 22th of May during the price safety margin of bitUSD was not enough, which resulted in a global settlement (“black swan event”). Selected witnesses abruptly stopped providing feeds for this assets, and despite the fact that the declared life time of the price feed is 24 hours, the mechanisms depending on the price feed stopped. After some time 2 feeds appeared, but the minimum required number is 3. Without feeds a manual asset revival is impossible, even if enough people want to bid on collateral for required amount. Abit announced (https://bitsharestalk.org/index.php?topic=33051.0) that the collateral bids will be ignored, and he will revive the asset himself. Apparently he disabled witnesses feeds from being accepted, so they would not interfere with his plans.

It is worth noting that once bitUSD encountered a black swan, hourly feeds for HERO private MPA were also stopped by terradacs-bp and liondani witnesses. It is not clear yet if that was manipulation, or reliance on bitUSD feeds.


Authors position
If you try to become a committee member, you will get a message that the position is unpaid.


Abits (https://github.com/abitmore) actions resulted in a creation of a funding stream towards committee account fueled by new fees. On one hand only BSIP-86 directly creates revenues for the committee, and is probably not in effect right now, however most of the trading happens in committee bitassets, so the fees paid to MPA owners go to committee in most cases.

Despite the lack of paid workers for development, updates of the core software are being developed, yet the display of the new fees in the UI are being delayed with responses in the vein of “we are not paid for it”.

In essence under the pretense of increasing the revenue of Bitshares as a DAC (Decentralized Autonomous Company) via the fee burn that would result in deflatory pressure, which is similar to the shares buyback by a company, that would result in the appreciation of BTS holders assets, the value flows were reformed in such a way, that most of the share (Market Fee) comes under control of the committee, that can be spent as they see fit. Where is the guarantee that the committee doesn’t block and unvote current members, to keep the status quo? Previous track record shows that on bitcrab’s suggestion under pretense of bitasset liquidity they have lost a lot of money by participating in margin trading. What will happen this time we are yet to see.

If we view Bitshares as a company, the committee as a Board of Directors, and BTS holders as stakeholders, then the stakeholders stock as unilaterally converted to preferred equity shares (non voting), and the Board of Directors is milking the company, leaving miniscule remainder of the market and transfer fees that go into reserve pool. The revenue of those “directors” is based on the hidden fees, that most users are not aware of yet.

Such a situation in a real company is nonsense and such activity is illegal in most countries. Abit and his team got scot free so far.

That is one side of the situation.

On another hand shareholders themselves (lets call them majority holders) before all this mess were methodically scamming the users (mainly bitasset holders) by not having enough collateral against their debt obligations (bitassets) effectively stealing from them. To stop this fraud shareholders themselves would have to accept losses and lose their voting assets. If we take into the account that most users did not understand the intricacies of the platform the HODLers weren’t paying enough attention to the situation, such an abuse from major debt holders did not result in BTS price decline that was adequate to the outrageousness of the situation. The status quo with fake asset feeds (BSIP-42) and milking the reserve through the workers were a gainful strategy for them.

But as they say there is more. The author of BSIP-42  (https://github.com/bitshares/bsips/blob/master/bsip-0042.md)is not bitcrab, but Abit. Everything he could reply when that was pointed out was “That is in the past”.

My opinion on the NewBitshares is only that the new blockchain received mainly the cunning chinese as its community, which were fine with feed manipulation on Bitshares, and I was and still am against such methods, I did not have the inclination to follow them there.

In closing
Since the new chain parameters are still not displayed in BitsharesUI, I decided to create a table with current parameters of main committee MPA’s including the new 1.0 ones.

Current bitasset parameters with “hidden” fees (https://golos.id/ru--blokcheijn/@akledirs/tekushie-parametry-bitassetov-so-skrytymi-komissiyami)