Author Topic: Hangout every Friday @ 10am EST/STD  (Read 189598 times)

0 Members and 1 Guest are viewing this topic.

jakub

  • Guest
Could BM comment of our recent community effort (led by @abit ) aimed at implementing percentage-based fees?
Is CNX willing to support it by reviewing the code and advising how to improve it in terms of code quality & efficiency?

Offline fuzzy

This will probably be answered when Dan gives the usual update but in case he doesn't mention it..

- The first milestone of the STEALTH implementation was scheduled to be finish around January 15th (today). We know there are always delays, could you tell us if you're close to achieve it?

- Could you sometime around this next week provide us with a budget on how much would Bond Markets cost us if you were to implement it? Even if a rough estimate. I think that would be interesting to know since it's something people have showed interest in. It would be cool to debate to see if the shareholders who use the forum think it's worth it vs the cost you present us with.
Edit: Noticed this was basically the same as Bhuz's last question.

WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline fuzzy

I think that eventually a lot of people in the community would like to know:

1) How much would it cost to implement a simple GUI for PM, making it easier and straightforward to use, hiding all the backend mechanics such as the need to borrow/sell etc.

2) Bond Market. Could we pay a couple of days of your time to make a general analysis about:
- Is it really feasible?
- How hard it would be and what are the biggest problems to work out?
- Some ideas to solve those problems.
- How many man hours would it need, and how much would it cost?

3) Bond Market with Margin Trading (lending + shorting the lended)
AFAIK one of the biggest problem basically is that since all the transactions/lending would be publicly viewable on the blockchain, an attacker could see exactly how much money he need to cause a margin call?
-About this, could the STEALTH feature be used to hide this sensitive data and solve that problem?

Edit: made some edits here and there xD

https://bitsharestalk.org/index.php/topic,21014.0.html
WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

jakub

  • Guest
@fuzzy , would you consider asking questions listed in OP of this thread?
https://bitsharestalk.org/index.php/topic,20634.0.html

In case all 4 of them are too much, I'm especially interested in question (3), which boils down to this:
For SmartCoins and UIAs whose value against BTS is known at any point in time, could we introduce a BTS value threshold below which the transfer fee is very low?

Example for bitUSD, assuming the BTS value threshold is 1000 BTS:
- if I transfer an amount of bitUSD whose value in terms of BTS is lower than 1000 BTS, I pay only 5 BTS for the transfer fee
- if I transfer an amount of bitUSD whose value in terms of BTS is equal or higher than 1000 BTS, I pay 30 BTS for the transfer fee (as we have it now)

This way we could:
- create a friendly environment for business based on receiving small tips
- still maintain a solid financial basis for the referral program

Offline fuzzy

Fuzzy, could you keep the discussions to be only about Bitshares (or at least mostly)? If you want to discuss about curiosume, you could have a special hangout for it. I'm not interested in it so I would like to have dev hangouts only for Bitshares related stuff.

I like hearing about other projects, but only if they are closely connected with Bit Shares.

Good, because the more project heads we help with beyond bitcoin to get the message out, the more developers will stay here as opposed to going to places they see as more open and accepting  :)
WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline fuzzy

Fuzzy, could you keep the discussions to be only about Bitshares (or at least mostly)? If you want to discuss about curiosume, you could have a special hangout for it. I'm not interested in it so I would like to have dev hangouts only for Bitshares related stuff.

As people join and speak, they are more than welcome to do so.  If that person is running a project that has strong intentions of working along with bitshares, then I am glad they are there and using the service to get recognized by the community.  BM has openly stated he plans to slowly step back from being the sole leader in the bitshares ecosystem and has structured the governance structures in such a way that we should be bringing as many people onboard as possible to start trying to lift some of the weight Dan has.  So in short, if someone is planning on developing something that is "powered by bitshares", then essentially we still are talking about bitshares.  For instance, Dan Robles wants to build curiosome as a bitshares-powered platform...which will essentially take much of the bias out of contracts for worker proposals for bitshares in the future.  He is heading up the National Society of Professional Engineers' (NSPE) blockchain division and is wondering right now if he wants to go with ethereum or bitshares.  Should I risk telling him he should not speak up considering that A) he might have something valuable to say that we have not recognized, B) he might be trying to secretly give us insight into what would make him choose us over ethereum, C) that he should start his own hangouts if he wants to talk about his project before he is even comfortable speaking out with a few sentences to the community?  I hope that answers your question.  This is all bitshares---but only if we let it.  If we push anything away that isn't "bitshares" as we perceive it, then I fear we will never have other devs and brilliant minds coming here to compete with other brilliant minds to make bitshares extremely valuable...

we have to think...bigger :P

As for other hangouts, we do have them, and plan on having more (just like taulant's). 
WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline Samupaha

  • Sr. Member
  • ****
  • Posts: 479
    • View Profile
  • BitShares: samupaha
Fuzzy, could you keep the discussions to be only about Bitshares (or at least mostly)? If you want to discuss about curiosume, you could have a special hangout for it. I'm not interested in it so I would like to have dev hangouts only for Bitshares related stuff.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
What is the status of fixing the bug that prohibits witnesses being able to withdraw pay?

Will that require a hard fork? What is the ETA of the fix?

related to the referral bug. no one can withdraw until this is fixed with a hardfork (bm mentioned this in the last hangout)

Offline Thom

What is the status of fixing the bug that prohibits witnesses being able to withdraw pay?

Will that require a hard fork? What is the ETA of the fix?
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Tuck Fheman

  • Guest
At the end of the hangout today we were talking about the sharebits (http://www.sharebits.io/), and that's the  "Security Code". I used my "Bitsharestalk Username " as the Security Code and it seem to work. Don't know how to explain this right but,  I notice when I put my name in the  "Bitsharestalk Username" it slid up over the "Security Code". If you try it you'll see what I mean.

Put your Forum name in top field.
Put Security Code (Withdrawal code) in bottom field.

Ignore text prompts on right until fixed. ;)

Offline konelectric

At the end of the hangout today we were talking about the sharebits (http://www.sharebits.io/), and that's the  "Security Code". I used my "Bitsharestalk Username " as the Security Code and it seem to work. Don't know how to explain this right but,  I notice when I put my name in the  "Bitsharestalk Username" it slid up over the "Security Code". If you try it you'll see what I mean.
Tweeter: Konelectric. Steemit: Konelectric. Youtube: Patrick Konshak. Success Council: Yourship. Mumble: Yourship or Konelectric.

Offline rgcrypto

  • Hero Member
  • *****
  • Posts: 557
    • View Profile
    • Cryptoctopus Blog
Question to bytemaster:

What is your opinion of the privately funded blockchain feature idea and how would he see it being implemented so that the UIA are not considered securities?

Offline btstip

  • Hero Member
  • *****
  • Posts: 644
    • View Profile
  • BitShares: btstip-io
Hey twitter, here are the results of your tips...
  • betax: has been credited 88 OPENSESAME
  • Thom: has been credited 88 OPENSESAME
  • testz: has been credited 88 OPENSESAME
  • hadrian: has been credited 88 OPENSESAME
  • gchicken: has been credited 88 OPENSESAME
  • rgcrypto: has been credited 88 OPENSESAME
  • cube: has been credited 88 OPENSESAME
  • Frodo: has been credited 88 OPENSESAME
  • Luckybit: has been credited 88 OPENSESAME
  • abit: has been credited 88 OPENSESAME
  • tbone: has been credited 88 OPENSESAME
  • liondani: has been credited 88 OPENSESAME
  • thisisausername: has been credited 88 OPENSESAME
  • clayop: has been credited 88 OPENSESAME
  • fav: has been credited 88 OPENSESAME
  • Unosuke: has been credited 88 OPENSESAME
  • Fox: has been credited 88 OPENSESAME
  • werneo: has been credited 88 OPENSESAME
  • CryptoPrometheus: has been credited 88 OPENSESAME
  • yellowecho: has been credited 88 OPENSESAME
  • lovejoy: has been credited 88 OPENSESAME
  • dichalcog3n9d3: has been credited 88 OPENSESAME
  • pheonike: has been credited 88 OPENSESAME
  • DestBest: has been credited 88 OPENSESAME
  • spartako: has been credited 88 OPENSESAME
  • onceuponatime: has been credited 88 OPENSESAME
  • Tuck Fheman: has been credited 88 OPENSESAME
  • methodx: has been credited 88 OPENSESAME
  • lafona: has been credited 88 OPENSESAME
  • jakub: has been credited 88 OPENSESAME
  • rgrcrypto: has been credited 88 OPENSESAME
  • ingenesist: has been credited 88 OPENSESAME
  • JWF: has been credited 88 OPENSESAME
  • Topcandle: has been credited 88 OPENSESAME
  • bitbuckster: has been credited 88 OPENSESAME
  • jcalfee1: has been credited 88 OPENSESAME
  • iHashFury: has been credited 88 OPENSESAME
  • Beyond Bitcoin: has been credited 88 OPENSESAME
  • luca21: has been credited 88 OPENSESAME
  • luckybit: has been credited 88 OPENSESAME
  • EstefanTT: has been credited 88 OPENSESAME
  • JoeyD: has been credited 88 OPENSESAME
  • ebit: has been credited 88 OPENSESAME
  • fuzzy: has been credited 88 OPENSESAME
Curious about BtsTip? Visit us at http://btstip.io and start tipping BTS on https://bitsharestalk.org/ today!
Created by hybridd

Offline twitter

  • Sr. Member
  • ****
  • Posts: 279
    • View Profile
Tip to mumble attenders.....

#btstip "betax" 88 OPENSESAME (MUMBLE="betax")
#btstip "Thom" 88 OPENSESAME (MUMBLE="Thom")
#btstip "testz" 88 OPENSESAME (MUMBLE="testz")
#btstip "hadrian" 88 OPENSESAME (MUMBLE="hadrian")
#btstip "gchicken" 88 OPENSESAME (MUMBLE="gchicken")
#btstip "rgcrypto" 88 OPENSESAME (MUMBLE="CryptoOctopus")
#btstip "cube" 88 OPENSESAME (MUMBLE="cube")
#btstip "Frodo" 88 OPENSESAME (MUMBLE="Frodo")
#btstip "Luckybit" 88 OPENSESAME (MUMBLE="Luckybit2")
#btstip "abit" 88 OPENSESAME (MUMBLE="abit")
#btstip "tbone" 88 OPENSESAME (MUMBLE="tbone")
#btstip "liondani" 88 OPENSESAME (MUMBLE="delegate.liondani")
#btstip "thisisausername" 88 OPENSESAME (MUMBLE="tiau")

#btstip "clayop" 88 OPENSESAME (MUMBLE="clayop_jaewoo")
#btstip "fav" 88 OPENSESAME (MUMBLE="favdesu")
#btstip "Unosuke" 88 OPENSESAME (MUMBLE="unosuke")
#btstip "Fox" 88 OPENSESAME (MUMBLE="Fox")
#btstip "werneo" 88 OPENSESAME (MUMBLE="werneo")
#btstip "CryptoPrometheus" 88 OPENSESAME (MUMBLE="Crypto-Prometheus")
#btstip "yellowecho" 88 OPENSESAME (MUMBLE="yellowecho")
#btstip "lovejoy" 88 OPENSESAME (MUMBLE="bitscape")
#btstip "dichalcog3n9d3" 88 OPENSESAME (MUMBLE="dichalcog3nid3")
#btstip "pheonike" 88 OPENSESAME (MUMBLE="pheonike")
#btstip "DestBest" 88 OPENSESAME (MUMBLE="DestBest")
#btstip "spartako" 88 OPENSESAME (MUMBLE="spartako")
#btstip "onceuponatime" 88 OPENSESAME (MUMBLE="onceuponatime")
#btstip "Tuck Fheman" 88 OPENSESAME (MUMBLE="tuckfheman")
#btstip "methodx" 88 OPENSESAME (MUMBLE="methodx")
#btstip "lafona" 88 OPENSESAME (MUMBLE="lafona2")
#btstip "jakub" 88 OPENSESAME (MUMBLE="jakub")
#btstip "gchicken" 88 OPENSESAME (MUMBLE="gchicken")
#btstip "rgrcrypto" 88 OPENSESAME (MUMBLE="CryptoOctopus")
#btstip "ingenesist" 88 OPENSESAME (MUMBLE="ingenesist")
#btstip "hadrian" 88 OPENSESAME (MUMBLE="hadrian")
#btstip "ingenesist" 88 OPENSESAME (MUMBLE="ingenesist")
#btstip "JWF" 88 OPENSESAME (MUMBLE="Jwf-mobile")
#btstip "Topcandle" 88 OPENSESAME (MUMBLE="Sxis")
#btstip "bitbuckster" 88 OPENSESAME (MUMBLE="brindleswan")
#btstip "jcalfee1" 88 OPENSESAME (MUMBLE="jcalfee2")
#btstip "testz" 88 OPENSESAME (MUMBLE="testz")
#btstip "iHashFury" 88 OPENSESAME (MUMBLE="ihashfury")
#btstip "Beyond Bitcoin" 88 OPENSESAME (MUMBLE="James212")
#btstip "luca21" 88 OPENSESAME (MUMBLE="luca21")
#btstip "luckybit" 88 OPENSESAME (MUMBLE="luckybit2")
#btstip "Frodo" 88 OPENSESAME (MUMBLE="Frodo")
#btstip "EstefanTT" 88 OPENSESAME (MUMBLE="EstefanTT")
#btstip "JoeyD" 88 OPENSESAME (MUMBLE="JoeyD")
#btstip "ebit" 88 OPENSESAME (MUMBLE="ebit")
#btstip "fuzzy" 88 OPENSESAME (MUMBLE="fuzzy")
witness:

Offline Bhuz

  • Committee member
  • Sr. Member
  • *
  • Posts: 467
    • View Profile
  • BitShares: bhuz
I think bytemaster needs to explain "how" he intended to motivate exchanges to share order books. Through shared IOUs or by asking multiple exchanges to focus on a particular BitAsset?
From what I see, that dream is not going to become a reality if we keep taking the current route. We'll just end up having a bunch of illiquid IOUs.

@fuzzy , this^ looks like a perfect question for BM.

Absolutely, please @fuzzy find the time for this question too. On the last hangout too much questions were not asked.