Proposal for witnesses & committee (MPA Ruble)

[nmywn]

I don't understand why we need to do it?
Our MPA is already on the market.
We don't ask for permission, we're offering collaboration.

Ok, but:

We'll change RUBLE to BitRUBLE 1:1, and then close positions and stop price feed on RUBLE

So I gave you simplest solution to make it happen today.
You can even have "bitRUBLE" ("bit" is added in GUI layer anyway.)


It's more about eliminating single point of failure than asking for permission. For now, one account is in total control. If you can build multisig group that you and others can trust then you're in home. You don't need witnesses as feed producers either.

[alt]

this is real business owned by yourself,
in fact you never need to wait for bitRUB
if you want to resolved trusted issue, just need to give owner's priority to multi account trusted by RUSSIA community. @bitcrab should can give you much advice.
you have my support, as one of the most important thing for Bitshares development.

[blockchained]

You can transfer ownership to committee-account, if they agree.

Changing the issuer

The current issuer of an asset may transfer ownership of the asset to someone else by changing the issuer in the asset’s settings.

I don't understand why we need to do it?
Our MPA is already on the market.
We don't ask for permission, we're offering collaboration.

[yvv]

Committee already owns bitRub. They broke it and can't fix it for two years.

[nmywn]

You can transfer ownership to committee-account, if they agree.

Changing the issuer

The current issuer of an asset may transfer ownership of the asset to someone else by changing the issuer in the asset’s settings.

[yvv]

What happens when bitRUB goes active? What is the plan to transfer?

We'll change RUBLE to BitRUBLE 1:1, and then close positions and stop price feed on RUBLE

Just buy RUBLE and force settle it. This is easy to do.

As for OP subject: come on guys, we need to support this. Gateway in Russia can give BTS a huge boost.

[blockchained]

In awaiting of hardfork when bit bitRUB will become live, we started our MPA - RUBLE.  (http://cryptofresh.com/a/RUBLE)

We need RUBLE for our gateway(https://market.rudex.org/), but this is not the only reason why we started RUBLE MPA.
Another reason is to fix the bit.RUB we need a hardfork and the last one was a couple of years ago.

For this MPA RUBLE we chose an option to give a price feed by the list of 10 accounts.

Minimum feeds: 3


What happens when bitRUB goes active? What is the plan to transfer?

We'll change RUBLE to BitRUBLE 1:1, and then close positions and stop price feed on RUBLE



So we have a proposal for witnesses/committee out there:

- You wish to start a price feed on RUBLE (http://cryptofresh.com/a/RUBLE)
- You write down your witness/committee nickname
- We collect all (max. 9) nicknames of participants and put them on the list of those who gives a feeds for RUBLE
- You start a price feed for RUBLE
- We vote your witness/committee with our proxy


Why we chose this way to publish feeds? Because we want to vote on those who helps us to develop bitshares ecosystem and represent our interests



list of those who already wish to participate:

1. blckchnd
2. litvintech
3. sahkan-bitshares
4. on0tole*
5. delegate.baozi
6. rnglab
7. openledger-dc
8. wackou
9. verbaltech2
10. delegate.ihashfury

*For now, we are giving a price feed from 4 accounts (blckchnd, ruslan, on0tole smailer) to cover the minimum amount of price feeds, but if we’ll have a support from other 9 accounts (committee/witnesses) we’ll keep only our witness - blckchnd

As to the point that creating a privatized MPA is not the best way to get trust of the community, I’d like to point out, that we already did a lot to do just that, and also, since we are in decentralized environment, and it is technically difficult to resurrect bitRUB, we decided, that it would be better to do this, and explain ourselves after, than waiting. Our intent is to have an instrument that will be decentralized, and use it till bitRUB is resurrected, then we’ll switch over to that, but that was mentioned earlier.