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

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 ... 125
151
51% is a gross overestimate. Try a 13% attack; that's what bitshares is currently vulnerable to.

DPOS was designed without the realisation of  what voter apathy would actually mean for the security of the chain. Instead of being the most decentralised currency, it is currently the least decentralised with one account controlling 100% of the chain.

As unpopular as the penalty fee was, perhaps only the removal of dilution & re-introduction of the 5% inactivity penalty fee for not voting at with BTS balances will improve it. (Ideally with FBA's the majority of that fee can be used for voter rewards.)

DPOS was a nice experiment, but the requirement for active voting was a big oversight. Much simpler to just plain remove it all and go with a much simpler system, which simply ranks by stake.

152
I would just have the system pick the top N forging accounts (by stake) and use those automatically as the delegates.
Any guarantee that top stake holders or collateral holders run witness nodes?
The problem is some of those accounts aren't currently voting.

Notice I used the qualifier 'forging' in the description :)

153
51% is a gross overestimate. Try a 13% attack; that's what bitshares is currently vulnerable to.

DPOS was designed without the realisation of  what voter apathy would actually mean for the security of the chain. Instead of being the most decentralised currency, it is currently the least decentralised with one account controlling 100% of the chain.

Time to throw the referral system back to the flames of hell from which it came and implement a collateral bid system where the client automatically votes for the top 101 accounts that put up the most collateral denominated in BTS?

I would just have the system pick the top N forging accounts (by stake) and use those automatically as the delegates.

154
51% is a gross overestimate. Try a 13% attack; that's what bitshares is currently vulnerable to.

DPOS was designed without the realisation of  what voter apathy would actually mean for the security of the chain. Instead of being the most decentralised currency, it is currently the least decentralised with one account controlling 100% of the chain.

155
Percentage based transfer fees are completely untenable. Every single other coin in the world has a low, fixed fee for any amount sent, bitshares would lose out to the competition and it would be a PR nightmare. Percentage based trade fees on the other hand, are acceptable.

156
The memo key for that account is BTS1111111111111111111111111111111114T1Anm, and it appears to be the same for a few others I checked. I believe this means that it's impossible for anyone to read the memos.

Have you sent memos to collateral-holder accounts before?
Can you leave the memo blank as a workaround?

Oh, hmmmm, that's interesting. I had just assumed this was a completely normal account with a custom name. Why would it have an invalid memo key?

157
It appears to be particular to this destination account:

Quote
transfer metaexchangebtc usd-collateral-holder-453 10 BTS "test" true
transfer metaexchangebtc usd-collateral-holder-453 10 BTS "test" true
10 assert_exception: Assert Exception
my->_key != empty_pub:
    {}
    th_a  elliptic_secp256k1.cpp:118 serialize

    {"from":"metaexchangebtc","to":"usd-collateral-holder-453","amount":"10","asset_symbol":"BTS","memo":"test","broadcast":true}
    th_a  wallet.cpp:2002 transfer

I can't send to it from another account either:

Code: [Select]
transfer monsterer usd-collateral-holder-453 10 BTS "test" true
transfer monsterer usd-collateral-holder-453 10 BTS "test" true
10 assert_exception: Assert Exception
my->_key != empty_pub:
    {}
    th_a  elliptic_secp256k1.cpp:118 serialize

    {"from":"monsterer","to":"usd-collateral-holder-453","amount":"10","asset_symbol":"BTS","memo":"test","broadcast":true}
    th_a  wallet.cpp:2002 transfer

I can transfer to other account without issue.

I'm guessing this is related to the object id reindexing and subsequent patching?

158
maybe your wallet has been corrupted due to some hdd errors or something similar.
Have you tried recover your wallet from a backup or reimport your active private key?

Before I do that I'd like to know for sure what is going on here, because this only started happening after the latest release was deployed.

edit: this is the first Release build I've used (they've all been built in Debug before) - I'll switch over and see if that makes a difference. Doubt it, tho...

160
Really would appreciate some help here, metaexchange is unable to send BTS transactions because of this :(

161
General Discussion / Re: metaexchange off line
« on: December 17, 2015, 09:35:05 pm »
Restored

162
General Discussion / Re: New release 2.0.151209
« on: December 17, 2015, 09:24:21 pm »
I'm getting weird errors trying to send transactions in the latest build - help would be appreciated:

https://bitsharestalk.org/index.php/topic,20683.0.html

163
Service restored :)

164
General Discussion / Re: metaexchange off line
« on: December 17, 2015, 08:49:34 pm »
The site is experiencing an outage, I'm working to restore it.

165
Metaexchange is currently experiencing a site outage; please bare with us while we resolve it.

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 ... 125