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.
Audit of the platform
This task has become relevant after several cases of the blockhain shutdown. They were caused by mistakes that hasn't been discovered since the early days of the platform. We believe such mistakes still exist and this situation endangers the main features of the blockchain - its continuance and immutability. Even couple of hours of shutdown leads to financial losses (not to mention reputational cost). We will conduct audit along with development, but it will be our priority at first.
Changing the fee collection system
The most basic example will be the fee for cancelling of an order. If a user doesn't have enough funds, he cannot do this because the fee cannot be withheld from the order. We plan to fix this along with other issues that we will describe in a separate BSIP. Now we investigate how to implement this feature safely (e.g. there can be a situation when funds placed in the order are not sufficient to pay a fee - in that case it still won't be cancelled).
Flexible settings of trading access keys
The idea that was discussed for a long time. The BitShares is a trading platform in the first place. However, it lacks flexible settings of keys that allow to provide access to trading to a third-party, not exposing active keys at the same time. Of course, there can be duct tape solutions already, but we need something more solid.
Non-LTM referral & membership
Creation of the classic on-chain referral system. It will allow to invite new users without extra costs and unnecessary headache (unlike the implementation in the majority of other projects). What can be more useful than the growth of the user base?
At first we expect direct payments without an escrow.
First of all, we would like to present you the page with the main points from our core worker proposal. It includes the roadmap with the list of tasks that we consider important (please note that their order does not represent their priority). https://worker.graphenelab.io/
I invite anyone who doubts our competence and experience to take a look at our previous projects. Graphene Lab has worked for more than three years using the BitShares' code in our projects, including the change of consensus mechanism and adding new functionality (e.g. new referral system, rating system, credit contracts, etc).
I am sure you have watched the movie Saw...
It's the festive season and Christmas and New year is around the corner... So in the spirit of the season I wanted to do a BTS giveaway for the first persons to comment the correct prices of BTS in GDEX.BTC and GDEX.USDT on both Christmas and New year day.
I have picked these pairs because they are the most liquid pairs on the bitshares DEX currently... So here are the rules
1. The winner gets 50BTS for each correct prediction, i.e each pair has a 50BTS reward.
2. The first comment to predict the prices correctly will win the prize
3. Comment is one per person and only the first comment by the person will be considered
4. Commenters must be on the BTS telegram channel because that is where the winner will be announced, the winner shall contact me privately with his BTS account for payment.
5. There can be two winners one for each pair
6. The correct open price of BTS/GDEX.Pairs on Christmas day will receive 100BTS
7. The correct open price of BTS/GDEX.Pairs on New day will receive 100BTS
8. Christmas day predictions shall end by 12am on the 24th while New year day predictions will end by 12am on the 31st day of December.
Now I know the reward looks small but remember the movie Saw it's not really about the reward so don't let this thread down thanks.
chill everyone.
I believe it was just a mistake/misunderstanding. Votes have been reinstated.
QuoteI found a interest thing with the worker payment，when bbf pay bitcny to somebody, he will quick buy bts with it, and then transfer the bts to binance very very quickly, then dump it to get BTC.
It looks most of the developer didn't want to grab the bts(shitcoin) for one more minute, this is very funny for the bts holder.
So i suggest the worker payment will pay with “direct debit”, when someone finished a worker and want to get the payment, the payer must pay with “direct debit” in 12 weeks, evey week pay: the total payment/12.
Any idea how it could be implemented here?
Is the PDF posted above considered the full proposal with the intention to put it up for voting like that, or is that merely the team introduction?
We will release full offer after discussion with the community. It will include roadmap describing tasks we would like to implement and open positions for those members of the current team who want to work with us. Rates of the team that was already described in the current offer won't change.
But who is to blame that people are allowed in december to invoice for april and take a larger amount of BTS from the reserve pool as they would when invoicing in a timely manner?
Fox added now invoices for July where bitshares was on peak this year.
Instead we pay when BTS is on this years ATL making that we need to pay 3.5 times more BTS as if he would have added the invoices in a timely manner.
But instead many months old invoices are now being added into the weakest performing month for BTS.
The core team report is now blaming that there were not enough funds to work on full capacity (which is BS claim)
So how is a voter supposed to know if there are enough funds or not ?
