Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - xeroc

Pages: [1] 2 3 4 5 6 7 8 ... 849
1
Stakeholder Proposals / Re: [Worker] Reference faucet via BitShares.eu
« on: January 16, 2019, 08:15:00 pm »
if you use this repo:
https://github.com/bitshares/tapin

and point it to the testnet api (wss://node.testnet.bitshares.eu), it will setup a local faucet for testnet

2
Stakeholder Proposals / Re: [Worker] Reference faucet via BitShares.eu
« on: January 16, 2019, 12:55:49 pm »
Testnet:
faucet: https://faucet.testnet.bitshares.eu
prefix: TEST

Mainnet:
faucet: https://faucet.bitshares.eu
prefix: BTS

If you send a public key with the wrong prefix to the faucets, they will raise an error/exception.
Is that what you are looking for?

Could this worker help with this issue? https://github.com/bitshares/bitshares-ui/issues/1773
BitShares.eu will give you a warning (that will show nicely in the UI) in case you try to create an account with keys for a different blockchain.
From a faucet POV, we can only identify "wrong blockchain" by means of the "prefix" (the first characters in your public key, e.g. BTSxxxxxxx).
If someone sets up a private blockchain and uses the same BTS prefix, then there is no way if knowing the users wants those accounts to be created somewhere else - in fact, the keys are identical then!
Could you help with the documentation aspect of private faucet & testnet setup please? I hadn't realized that you'd get an error if you changed the prefix, in my past security research I was blocked by an inability to use a private faucet on my private testnet :/ I've probably registered 10 accounts on the public testnet instead of the private testnet during early attempts 😂

3
Stakeholder Proposals / Re: [Worker] Reference faucet via BitShares.eu
« on: January 14, 2019, 02:09:19 pm »
Could this worker help with this issue? https://github.com/bitshares/bitshares-ui/issues/1773
BitShares.eu will give you a warning (that will show nicely in the UI) in case you try to create an account with keys for a different blockchain.
From a faucet POV, we can only identify "wrong blockchain" by means of the "prefix" (the first characters in your public key, e.g. BTSxxxxxxx).
If someone sets up a private blockchain and uses the same BTS prefix, then there is no way if knowing the users wants those accounts to be created somewhere else - in fact, the keys are identical then!

4
The workers have been created and can now be voted!

5
Stakeholder Proposals / [Worker] Reference faucet via BitShares.eu
« on: January 11, 2019, 02:09:22 pm »
Dear BTS voters,

as you may be aware, BitShares.eu (BitShares Europe) provides the reference wallet for the
software as hosted on github.com. The costs so far have been covered by the infrastructure
program operated by Blockchain Projects. The faucet has been funded by the reserve pool
and rewards from the referral program are directed to the BTS reserve pool. Thus, we managed
to operated at quite some profit for the BTS holders of over 100,000 BTS.

To make value proposition clearer to the BTS voters, we decided to remove Blockchain Projects
from the equation and apply for a worker proposal directly to fund the faucet maintenance,
operations and further development.

Details can be found here:
https://www.bitshares.foundation/workers/2019-02-reference-faucet

Please consider your votes.
Constructive feedback is welcome

6
General Discussion / Re: bitusd peg
« on: January 11, 2019, 01:57:51 pm »
Read this:
https://steemit.com/bitshares/@bitshares.fdn/how-global-settlements-work

There is a bidding scheme in place (BSIP18) that allows to revive bitUSD faster

8
Ginve that there currently is refund400k (and only one refund100k) and the fact that
some community members have the desire to reduce the "inflation", I think
the entire community is best served by providing more flexibility when it comes
to voting and funding workers.

With that said, I have just today created a proposal (on-chain) for the committee to create
the following new workers:

- refund100k-1
- refund100k-2
- refund100k-3
- refund50k-1
- refund50k-2
- refund50k-3

These would be created by the committee account and refund the pay to the reserves in case they are approved.

That means, the new (finer) worker proposals serve the same purpose as refund400k but allow for more flexible decision
making for proxies and BTS voters in general.

Look forward to see discussion.


On a side node: The same proposal also creates a worker "threshold-bsip" which refunds 1 BTS per day.
The purpose is to have an independent worker proposal to consider BSIPs approved. There will be a separate
announcement to this one.

9
General Discussion / Re: happy new year!
« on: January 05, 2019, 01:14:31 pm »
happy new year!

10
Stakeholder Proposals / Re: [Witness Proposal] blckchnd
« on: January 05, 2019, 01:10:42 pm »
was about time for you to earn some income for you hard work!

11
Stakeholder Proposals / Re: Proxy: xeroc
« on: January 05, 2019, 01:09:20 pm »
since your are the biggest proxy who support crazybit
what's your thought about the feed price cheating?
I guess we all known how important the feed price is for us, and it's one of the mainy jobs for the witness.
but crazybit give us a 'fake' feed price.
here is his logic as I observe today:
every 5 minutes, he will check if his price equal the finally feed price(median price of all feed price),
if it's not, he change his price to the median price.

This is a very stupid strategy, it's cheat.
what's the thought of those who support him as a witness?
That is indeed a stupid strategy. I'll do some research. If this turns out to be his implementation. I'll remove my support, ofc.

12
@xeroc

 I believe that "Spokesperson" worker was wrongly named/defined and this is much better and more fitting proposal from BBF than previous one. Am I on the point ?

This is finally replacement for "legal opinion" and "spokesperson"? If yes, then I personally support this worker for option 3) aka "Approval for the entire 12 months".

If not, please clarify more. Thanks!
Correct. With "spokesperson", people expected the BBF to be much more proactive than it has resources for. For instance, some community members expected the BBF to attend conferences around the world, do marketing for the BItShares Blockchain. Interestingly, even when there were opportunities (funded differently) for the spokesperson to attend conferences and do marketing about BitShares, the community wasn't very happy with it. So, what can be learned from this is to be more accurate with what the role is supposed to do. Hopefully, it is more clear now.

Funds are used to cover *time* spend by the entire team on aspects relevant to the work as representative. That mostly involves discussions and talking to third partners that desire to understand more abut the technology and legal aspects around BitShares and BTS. Unfortunately, NDAs prevent us from naming those businesses explicitly, but at least Bittrex is publicly known to be part of this list.
In case the worker is approved and later disapproved, no funding is available, hence, the BBF can still keep the mandate but has to stop spending time.

13
Stakeholder Proposals / Re: Proxy: xeroc
« on: December 31, 2018, 10:05:01 am »
Wish you happy holidays
Thanks.

Due to the need for legal mandate, I took a break from my break and approved the worker proposal to grant a mandate to the BBF for legal representation:
https://www.bitshares.foundation/workers/2019-01-legal-representative

14
There is now a subsequent worker proposal to at least obtain a mandate for the BitShares Blockchain Foundation:
Details:
https://www.bitshares.foundation/workers/2019-01-legal-representative

15
Stakeholder Proposals / Re: Proxy: xeroc
« on: December 26, 2018, 01:57:43 pm »
I just removed my vote from witnesses xn-delegate, roelandp, and xman as they are feeding CNY prices that are more than 8% off.
gdex-witness promised to fix their feed script shortly.
I have also removed openledger-dc since they feed a USD price that is almost 20% off.

Also, I would like to let the community know that I will be most away from keyboard until January 6th.

See you all at 7th :D

Pages: [1] 2 3 4 5 6 7 8 ... 849