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 - R

Pages: 1 ... 50 51 52 53 54 55 56 [57] 58 59 60 61 62 63 64 ... 68
841
General Discussion / Re: DNS
« on: June 21, 2017, 09:27:58 pm »
l did ask them quite  a few times this is Bter last repond
The BTS for DNS is yet to be distributed


If that's what they're telling you, then they're lying.

842

The BSIP doesn't provide a solution to Yield Harvesting because it doesn't create the issue in the first place. Profits would be sharedropped onto asset holders on a scheduled basis; this proposal is not vulnerable to the 'Yield Harvesting' issue that 'Socialized yield' was.

Please explain. AFAICS BSIP-0019 proposes to pay dividends on bitassets (among others).

What stops me from using my BTS for shorting bitassets into existence and keeping them in my wallet, with the goal of collecting dividends for them?

There's nothing preventing you locking up your BTS as smartcoins for the long term, by doing so you are removing BTS from the liquid supply and become eligible for earning dividends.

To avoid abuse of this mechanism we could evaluate the average asset holdings since the last dividend payment or only allocate dividends for the time that these assets have been in an user's wallet for (if the user has held the coins 14 of 30 days in a 30day dividend schedule, they only receive the 14days worth of dividends).

843
AFAIK the recent profit of our DAC stems from a giant refund paid by Xeroc's worker. We're far from a situation where the fees regularly exceed our costs.

Your BSIP lacks a solution to the Yield Harvesting problem.
The previous estimate of 1 million BTS in fees per month is approx $320k, given that value was $6k when this thread started I believe the proposal is even more viable. It's up to the committee to figure out fees pegged to the dollar/cny so that we have accurate witness pay (and increased profitability of the DEX).

The BSIP doesn't provide a solution to Yield Harvesting because it doesn't create the issue in the first place. Profits would be sharedropped onto asset holders on a scheduled basis; this proposal is not vulnerable to the 'Yield Harvesting' issue that 'Socialized yield' was.

---

I'm splitting the BSIP in two - one for UIA, another for MPA.

845
Count me in!

I'll replicate my post from steemit:

Bitshares Roadmap?

Could we update the Bitshares roadmap https://bitshares.org/roadmap.html ?  The last entry in the current roadmap on the official bitshares website is Feb 2016.

Funding BSIPs/Worker proposals!
We've got this massive reserve pool of funds to potentially fund development - it's literally in the hundreds of millions $ range!

Some may argue that users who fear BTS dilution will reject all worker proposals, however I believe this was only the case a couple years ago for Bytemaster due to political reasons. Given how less BTS will be distributed now due to the current marketcap, this may not be as serious of a concern anymore.

I feel that there are two things blocking worker proposal attempts:
* Inability to create worker proposal via the GUI. ([Bitshares-UI issue raised!](https://github.com/bitshares/bitshares-ui/issues/173)
* Having to create a worker proposal to request funds for potentially developing features for the Bitshares DEX. I feel that requesting payment may be a daunting task, putting users off. If we were able to create bounty proposals to advertise the need and support of a potential [BSIP](https://github.com/bitshares/bsips) we'll successfully recruit developers. Thoughts?

Writing up BSIPs after discussion!
After coming up with a great idea, or holding a discussion about a possible idea we need to make a habit of writing up a [BSIP](https://github.com/bitshares/bsips) to get action going on new features.

Case and point, I still need to write up a BSIP for 'Earning interest/dividends on bitassets' (The forum post has 3000+ views and 9 pages! https://bitsharestalk.org/index.php/topic,23981.0.html)

Shoutout to BSIPs
https://github.com/bitshares/bsips/blob/master/bsip-0017.md (Revive BitAssets after global settlement - Peter Conrad; Stagnated.)
https://github.com/bitshares/bsips/blob/master/bsip-0018.md (Revive BitAsset through buying Settlement Pool - Fabian Schuh; New!)
https://github.com/bitshares/bsips/blob/master/bsip-0005.md (Expiring Votes for Witnesses - Fabian Schuh; Stagnated.).

846
Yes. Bitshares should be one of the main exchanges that PPY is traded on!

847
General Discussion / Re: HERTZ - Oscillating Formula Based Asset
« on: June 07, 2017, 06:38:23 pm »
Wackao responded to the Github Issue: https://github.com/wackou/bts_tools/issues/24#issuecomment-306741609
"Thanks for the suggestion, I like the idea! Not sure if it's going to be useful (don't have enough understanding of economics yet), but just the fact that we are able to try things like that on BitShares is plain awesome.
A bit busy with the launch of PeerPlays right now, but I'll give it a try soon :)"

848
General Discussion / Re: HERTZ - Oscillating Formula Based Asset
« on: June 05, 2017, 11:06:25 pm »
https://github.com/grctest/HERTZ-Price-feed-script/blob/master/min_hertz.hs

I have created a simplified version of the Haskell HERTZ price feed script.

The script no longer scrapes cryptofresh for asset values, doesn't handle json, doesn't output to CSV nor use the turtle library.

The script now runs from the command line and takes 5 arguments:
Code: [Select]
./min_hertz.hs referenceBlock genesisBlock blocksInPeriod amplitude referenceAssetValue
example: ./min_hertz.hs 50 1 100 0.5 25
output: 25.784882

Since you can now enter values easily from the command line as arguments, it will be easier for everyone to test out their own hertz configurations (different frequencies, amplitudes and backing assets).

Any suggestions?

Steemit mirror: https://steemit.com/beyondbitcoin/@cm-steem/hertz-haskell-price-feed-script-update

849
General Discussion / Re: HERTZ - Oscillating Formula Based Asset
« on: June 02, 2017, 02:01:19 pm »
It's be great if the price feed publishing fees were free so that we could have very high frequency HERTZ tokens.

850
General Discussion / Re: HERTZ - Oscillating Formula Based Asset
« on: May 31, 2017, 04:29:15 pm »
I've created issues for HERTZ potential inclusion in xeroc & wackou's price feed scripts (both use python)

https://github.com/wackou/bts_tools/issues/24
https://github.com/xeroc/bitshares-pricefeed/issues/3

851
General Discussion / Re: Will it be love?
« on: May 31, 2017, 12:13:04 am »
I'll be honest, I don't think stealth features align with the next wave of investors.

I firmly believe the first bitcoin run several years ago was driven by people who were on the bleeding edge of tech. I think the wave of people coming into crypto now is the bleeding edge of finance.

I think these people are going to be traders, hedge funds, venture capital, mutual funds.

They are familiar with trading technologies. They are familiar with transactions per second. (things bitshares has) Secret transactions are not critical to them because they don't exist in our current banking world.

Stealth transactions are not important to the future of bitshares.

Why are stealth transactions valuable to the groups listed?  traders, hedge funds, venture capital, mutual funds
I do think stealth is needed to take marketcap from the anon cryptos, as to why they would want private trading - they might not want their every trade data mined? It is a public ledger after all..

Can you buy stealth tokens? I'd love to own a stake..

852
General Discussion / Re: btsbots wallet release v0.0.1
« on: May 30, 2017, 04:44:00 pm »
Can't login? Not getting any warning, just doesn't log in. (No 'wrong password' password when using the right pass).

853
General Discussion / Re: HERTZ - Oscillating Formula Based Asset
« on: May 29, 2017, 01:08:59 pm »
Since CNY is one of the most popular smartcoins on the BTS DEX, perhaps it would be wise to use it as the reference asset instead of USD and/or XDR.

It appears to be leading the poll at the moment too.

854
General Discussion / Re: BlockPay in Serious Trouble
« on: May 27, 2017, 06:33:19 pm »
RE - "disrupting" mumble. My goal in challenging chris4210 was NOT to disrupt the mumble. In fact, it wasn't until 40 minutes into it this discussion occurred. With such an important issue we shouldn't restrict the discussion, and Friday mumble is the perfect venue to make people aware of what is going on. On that note mission accomplished. If that means some topics aren't discussed this week so be it. 1 hour is obviously not enough time to cover everything. I will admit it might have been better had onceupoonatime posted in the beyondbitcoin steemit article that fuzzy publishes each week to officially get on the bbc agenda, but that was addressed in the opening moments when chris / fuzzy asked the audience if other topics should be added to the agenda. So the discussion of stealth was introduced properly and acknowledged as an agenda item that way.

I did not mean to imply that you were disrupting the mumble session, I meant that if we were to all ask in the mumble about this topic one after another we would only get 'no comment' from Chris. I do agree that it's a serious issue that needs resolved, but he's simply not going to divulge anything productive in public (other than fud - eg rebranding/reissuing tokens).

RE - the lack of community interest. I simply don't see many people even willing to ask questions about this mess. @pc in the forum actually said it's not good to make this public. ALL IT TAKES FOR EVIL TO PROSPER IS FOR GOOD MEN TO DO NOTHING. If this were happening to you wouldn't you want the truth to be known? Those wanting to do evil thrive in the darkness of secrecy and it's important to shine a light of truth on them to expose them. How hard can it be to ask a question?
Perhaps because it's really negative and none of us were expecting this mess when we originally invested in Blockpay? If I was a developer who had his pay cut because of a quarrel between my bosses I'd be livid; it's disgusting to withhold employees salaries, doing so is a serious warning that something is wrong (perhaps even breaching EU work rights?). If I was Chris I'd be asking others to host the hangout to avoid the public spotlight until this is all sorted out...

855
We should have a dynamic fee mechanism where we state 'the fees will always be $0.01' (for example) and the settings are automatically adjusted for the exchange rate of BTS.
The majority of the DEX's income comes from registering assets/accounts and LTM, network transactions are a minority and BTS would probably benefit from them being made almost free.

Pages: 1 ... 50 51 52 53 54 55 56 [57] 58 59 60 61 62 63 64 ... 68