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 - BunkerChainLabs-DataSecurityNode

Pages: 1 ... 23 24 25 26 27 28 29 [30] 31 32 33 34 35 36 37 ... 168
436
I agree that $150 is way too high.  [...] The cost should be just high enough to ensure serious proposals, but without being a barrier.  Don't forget that a cost like this will be more of a barrier in some localities than in others.  So I think $25 would be a better starting point.  If we get too many unserious proposals, then we can raise it in the future.  But I doubt we'd need to.
 
+1
+5% I totally agree. It is not in BitShares interest to deter or make prohibitive making worker proposals. We need development.
1. Please keep in mind that lifetime members get 80% cash-back. Worker proposal is a LTM-only feature. So a 150$ creation fee means $30 for them. Is it really that expensive? Or you're just too miserly/lazy? If you're able to get your worker voted in, you can always ask for reimbursement of the worker creation fee by including it in the payment.

2. If we don't set a barrier on the creation of workers, funds in the reserve pool can be stolen much more easily. If alt withdraw his votes from the refund workers NOW, every LTM can create a worker with whatever amount of payment and vote for herself and get paid FROM NEXT HOUR, no need to beg for other stake holders' approval. And worse, she can create a worker every hour so others have no chance to vote against her. And even worse, she can create more than 1000 workers so technically no one can vote against all these workers. Current design of worker feature is flawed, the only way we can secure it is the fee.

Makes sense?

Thanks for mentioning the LTM factor.

Having to be an LTM in order to post a Worker is something at face value is not easily factored in.

At a $50 rate it ends up being $10 for a Worker and a 90 day vesting for them to get their $40 back. At $150 they are vesting $120.

While $150 on it's face is really does appear on the high end, it shows that some of the fee schedules we are dealing with can only be understood in light of the LTM being applied to understand the true price.

If there is an effective way for us to communicate this so that on it's face it doesn't have the same reactions we see filling this thread, then we can probably better handle it.

With the scale of economies on one end $50 with $10 being the true cost, the $150 with $30 being the true cost is still within proximity to what I think would be ideal.

To be clear this particular fee I do not think should be a reason for not approving the current proposal. I do however want to see a way to communicate the LTM-only related fees more clearly. For the sake of future Workers I think it will be an important element in the messaging to be considered.

437
Hi,

Can you please provide more details as to what happened?

Were there specific error messages?

If so, could you possibly provide some screenshots to show it 'not working' ?

Hopefully we can figure out what is going wrong quickly.

438
@committee: The proposal has been published and will expire in 7 days:     1.10.96
(Do not vote for 95, it has bugs that resulted from integer forcing fees for convenience, we can fix that later on)

This is how the proposal compares to the current fees:
Code: [Select]
        price_per_kbyte price for                                  transfer differs by    0.113x (network:    0.0882 USD / proposal:    0.0100 USD)
                    fee price for                                  transfer differs by    0.136x (network:    0.1324 USD / proposal:    0.0180 USD)
                    fee price for                        limit_order_create differs by    0.023x (network:    0.0441 USD / proposal:    0.0010 USD)
                    fee price for                        limit_order_cancel differs by    0.227x (network:    0.0004 USD / proposal:    0.0001 USD)
                    fee price for                         call_order_update differs by    0.227x (network:    0.0044 USD / proposal:    0.0010 USD)
            premium_fee price for                            account_create differs by    0.283x (network:   17.6489 USD / proposal:    5.0000 USD)
              basic_fee price for                            account_create differs by    0.239x (network:    0.4192 USD / proposal:    0.1000 USD)
        price_per_kbyte price for                            account_create differs by    0.793x (network:    0.0088 USD / proposal:    0.0070 USD)
        price_per_kbyte price for                            account_update differs by    0.793x (network:    0.0088 USD / proposal:    0.0070 USD)
                    fee price for                            account_update differs by    0.227x (network:    0.0044 USD / proposal:    0.0010 USD)
                    fee price for                         account_whitelist differs by    3.777x (network:    0.0265 USD / proposal:    0.1000 USD)
membership_lifetime_fee price for                           account_upgrade differs by    1.360x (network:   88.2446 USD / proposal:  120.0000 USD)
  membership_annual_fee price for                           account_upgrade differs by    0.850x (network:   17.6489 USD / proposal:   15.0000 USD)
                    fee price for                          account_transfer differs by    1.133x (network:    4.4122 USD / proposal:    5.0000 USD)
                symbol3 price for                              asset_create differs by    1.813x (network: 4412.2282 USD / proposal: 8000.0000 USD)
            long_symbol price for                              asset_create differs by    2.266x (network:   22.0611 USD / proposal:   50.0000 USD)
                symbol4 price for                              asset_create differs by    1.743x (network: 1147.1793 USD / proposal: 2000.0000 USD)
        price_per_kbyte price for                              asset_create differs by    1.133x (network:    0.0088 USD / proposal:    0.0100 USD)
        price_per_kbyte price for                              asset_update differs by    0.793x (network:    0.0088 USD / proposal:    0.0070 USD)
                    fee price for                              asset_update differs by   22.664x (network:    0.0882 USD / proposal:    2.0000 USD)
                    fee price for                     asset_update_bitasset differs by    1.133x (network:    4.4122 USD / proposal:    5.0000 USD)
                    fee price for               asset_update_feed_producers differs by    1.133x (network:    4.4122 USD / proposal:    5.0000 USD)
        price_per_kbyte price for                               asset_issue differs by    0.793x (network:    0.0088 USD / proposal:    0.0070 USD)
                    fee price for                               asset_issue differs by    5.666x (network:    0.1765 USD / proposal:    1.0000 USD)
                    fee price for                             asset_reserve differs by    5.666x (network:    0.1765 USD / proposal:    1.0000 USD)
                    fee price for                       asset_fund_fee_pool differs by   56.661x (network:    0.0088 USD / proposal:    0.5000 USD)
                    fee price for                              asset_settle differs by    0.057x (network:    0.8824 USD / proposal:    0.0500 USD)
                    fee price for                       asset_global_settle differs by    1.133x (network:    4.4122 USD / proposal:    5.0000 USD)
                    fee price for                        asset_publish_feed differs by    0.227x (network:    0.0004 USD / proposal:    0.0001 USD)
                    fee price for                            witness_create differs by    1.133x (network:   44.1223 USD / proposal:   50.0000 USD)
                    fee price for                            witness_update differs by    0.057x (network:    0.1765 USD / proposal:    0.0100 USD)
        price_per_kbyte price for                           proposal_create differs by    5.666x (network:    0.0088 USD / proposal:    0.0500 USD)
                    fee price for                           proposal_create differs by    0.850x (network:    0.1765 USD / proposal:    0.1500 USD)
        price_per_kbyte price for                           proposal_update differs by    0.793x (network:    0.0088 USD / proposal:    0.0070 USD)
                    fee price for                           proposal_update differs by    0.567x (network:    0.0088 USD / proposal:    0.0050 USD)
                    fee price for                           proposal_delete differs by    0.000x (network:    0.0088 USD / proposal:    0.0000 USD)
                    fee price for                withdraw_permission_create differs by   16.998x (network:    0.0088 USD / proposal:    0.1500 USD)
                    fee price for                withdraw_permission_update differs by    0.057x (network:    0.1765 USD / proposal:    0.0100 USD)
        price_per_kbyte price for                 withdraw_permission_claim differs by    0.793x (network:    0.0088 USD / proposal:    0.0070 USD)
                    fee price for                 withdraw_permission_claim differs by  999.000x (network:    0.0000 USD / proposal:    0.0144 USD)
                    fee price for                withdraw_permission_delete differs by    0.000x (network:   44.1223 USD / proposal:    0.0000 USD)
                    fee price for                   committee_member_create differs by  566.607x (network:    0.0088 USD / proposal:    5.0000 USD)
                    fee price for                   committee_member_update differs by 1133.214x (network:    0.0088 USD / proposal:   10.0000 USD)
                    fee price for committee_member_update_global_parameters differs by    0.000x (network:    0.1765 USD / proposal:    0.0000 USD)
                    fee price for                    vesting_balance_create differs by    0.113x (network:   44.1223 USD / proposal:    5.0000 USD)
                    fee price for                  vesting_balance_withdraw differs by  226.643x (network:    0.0088 USD / proposal:    2.0000 USD)
                    fee price for                             worker_create differs by 16998.214x (network:    0.0088 USD / proposal:  150.0000 USD)
        price_per_kbyte price for                                    custom differs by    1.133x (network:    0.0088 USD / proposal:    0.0100 USD)
                    fee price for                                    custom differs by   11.332x (network:    0.0088 USD / proposal:    0.1000 USD)
                    fee price for                                    assert differs by   56.661x (network:    0.1765 USD / proposal:   10.0000 USD)
        price_per_kbyte price for                         override_transfer differs by    0.793x (network:    0.0088 USD / proposal:    0.0070 USD)
                    fee price for                         override_transfer differs by   22.664x (network:    0.0441 USD / proposal:    1.0000 USD)
       price_per_output price for                         transfer_to_blind differs by    0.793x (network:    0.0882 USD / proposal:    0.0700 USD)
                    fee price for                         transfer_to_blind differs by    2.380x (network:    0.0882 USD / proposal:    0.2100 USD)
                    fee price for                       transfer_from_blind differs by    2.380x (network:    0.0882 USD / proposal:    0.2100 USD)

Note, that currently there is a discussion among some committee members whether the proposed $150 for creating a fee is too high.
I encourage committee members and shareholders to take a position and tell us what they think but keep in mind that changing a fee now will only result in a delay of at least another 7 days.

Thanks Xeroc!

Regarding the cost of creating a worker proposal being set to $150, I think considering we need more workers from around the world, the $150 premium is very prohibitive of getting any competing offers from weaker economy countries where dev work could be less.

I also think that there should be a premium to ensure the applications are serious and committed and also regarding the potential attack vector.

A premium should also send a signal to everyone who votes that someone was serious enough to put up money for the work they are going to perform should be given a fair review for voter support.

Therefore, with consideration of scale of economies, I am recommending $50  be the cost for the creation of a Worker.

Looking forward to other thoughts on this.

439
no enough  active  users
no real  liquidity!!!!!!!!!!!

OK... then get to work and send them here quick for free and stop the madness !!!!!!!!!!!

440
General Discussion / Re: Introducing Cryptonomex International (CNI)
« on: February 23, 2016, 06:15:16 pm »
Counter Negativity Measure Deploy!



441
General Discussion / Re: Introducing Cryptonomex International (CNI)
« on: February 23, 2016, 03:00:43 pm »
Back on track: I have met both, Manuela and Ronald in Amsterdam. It's been the main motivation for me to go there from the beginning.
We have had quite some nice talking about how to bring CNX/CNI and BTS more exposure.

For those that cannot read between the lines: I will be a part of CNI as a technical consultant and also contribute as business developer.

That is also what we did during d10e in Amsterdam. I had quite some talks with businesses, investors and others and usually started of telling them about
our toolkit to deploy blockchains (graphene) and quickly told them why they shouldn't deploy their own chain (shared user base etc).
In the end, most have been very excited already when I told them about market pegged assets. After telling them about turing completeness, confirmation
times, FBA, and 0-fee transfers most went crazy.

In short, we have an awesome product, we just need to start selling it to people and that is what I plan to do.

Awesome stuff!  +5%

442
Only product that you are aware off.

I was about to say the same. :) ... We have already been told about things like Plasma.. but there are other things they could be working on or focused on now that they are no longer welcome here if the forum remarks are any barometer on that matter. Sad really.

443
General Discussion / Re: Hyperledger Contributions
« on: February 23, 2016, 02:52:34 pm »
If they address privacy issue properly, their blockchain will be the king.

No not really. Just because big corporate names are behind it that doesn't mean it's a good architecture.

Big names is not what matters the most. Privacy is a must have feature for business. Private mode should be the default mode. And these guys from hyperledger claim that they have some solution.

We have seen what the big names ideas of privacy are like.... and what happens when gov wants a backdoor... anybody want an Apple? How about those Juniper routers?

This isn't about getting privacy right.. it's more about setting the standard that everyone else will need to comply with.. even if we don't like that standard. At least that's more along the lines of how it looks to me anyways.

444
General Discussion / Re: bitSHARES - As True Shares and Not a Currency!
« on: February 23, 2016, 02:47:16 pm »
Why don't we have a one time event.. say for 60 days.. where people will be PAID to remove their orders from the exchanges back to their own accounts in preparation for the transfer cut off update?

I think two months and perhaps a small dedicated full time team just constantly every day telling everyone to do it will ensure everyone gets their balances back in their hands and then at the end of 60 days.. fork the change.

I have no idea how much to pay.. lets just say +5%.

Needs more work on the details.. but just putting it out there.

445
Would being a bitcoin / ethereum sidechain reduce bitshares security?

If the value of btc held in multisig by witnesses becomes significant compared to their stake in bitshares, wouldn't they have the incentive to collude and take the btc and other possible coins like eth.

As the holding of BTC increases in the bitshares network so would the value of BTS... therefore the witness pay will also increase.

Aside from this, it may raise the bar for witnesses to have to be more serious participants or increase certain standards of operations and more importantly... have a known reputation of trust. Witnesses now are generally people already know from years past and even I don't know who they all are... which is a good thing in a way... even less likelihood of collusion.

I can tell you as a witness we would never risk our company name being tarnished in such a scandal. If the design is how I think it will be, it will require ALL active witnesses to be participants in the collusion to steal BTC.

446

This means that your team should actively help Theo on fixing and closing issues, not just pay him extra. I assume that Theo, being a CNX's dev, is already paid for his work.

I would like to see you/your team really making commits and fixing issues. This is what the shareholders expect from this worker IMO.

This assumption was already negatived in previous statements. We are a DAC and our only working manpower is what comes through the Workers.. the expectation of free labourers from CNX is not a reasonable assumption.

Negatived? You mean rejected?

Doesn't matter if you guys keep saying CNX shouldn't be expected to work on Graphene "for free", I certainly feel they should as it's in their interest (and I'm even a founding member and stock holder), and I'm pretty sure most people around here also think they should.

Sorry I meant negated... just woke up after only a few hrs sleep :)  Corrected.

In regards to free work.. where exactly should the funds come from then for them to work 'for free' if this is the case. I like to understand how their business model for man-hours should be paid then. What are the more ideal solutions that can work better?

447

This means that your team should actively help Theo on fixing and closing issues, not just pay him extra. I assume that Theo, being a CNX's dev, is already paid for his work.

I would like to see you/your team really making commits and fixing issues. This is what the shareholders expect from this worker IMO.

This assumption was already negated in previous statements. We are a DAC and our only working manpower is what comes through the Workers.. the expectation of free labourers from CNX is not a reasonable assumption.

448
General Discussion / Re: bitSHARES - As True Shares and Not a Currency!
« on: February 23, 2016, 07:46:51 am »
Mostly caught up on this thread...

It's a smart idea with many benefits. If I understand correctly, the only change required to make this happen is to simply disallow transfers of asset 1.3.0 (core asset).. this could theoretically be accomplished by adding a single line of code, no? (assert asset_id != 1.3.0 for transfer_op)

But I don't think it's wise to create a fork and fragment our resources at this point.. is some form of hybrid approach/compromise? For example.. I threw out the idea a while back to create a separate BTSVOTE token and sharedrop it 1:1 on BTS. BTS would no longer be used for voting, and exchanges could sell their BTSVOTE tokens to whoever valued them more. This way, they would be fairly compensated for giving up their ability to vote. (Not that I think this is necessarily practical but more of a thought experiment)

Something like this.. but in reverse perhaps? Graphene when it was being developed had the CORE asset being used. Going into Bitshares it was switched to BTS.

What if we performed a hardfork that swiched the CORE asset in the network from BTS, to a new symbol.. and THAT would be the one that is non-transferable with a 1:1 sharedrop on everyone minus the exchanges balances.

BTS can continue to trade as the 'coin'

A new non-transferable unit could be used as the backing. Lets call it HODL :)

By resetting the core asset of the network to becoming something new with a 1:1 sharedrop we are basically letting BTS fend for itself in the wild while the new HODL becomes the bedrock to all assets.

It's so easy to say this in a forum post.. but I have a fair idea of the numerous operations that are going to be involved in switching this that are going to give BM a minor anxiety attack.

We got plenty of time to continue to debate over various ideas.. whatever happens shouldn't be taking place for at least another 6-7 months anyways.

449
Just for the record, DSHARES was the original name for my early ideas on stable crypto...

https://bitcointalk.org/index.php?topic=213588.0

 ;D

Hey check it out.. the new dshares is only a 3 year step back in time. :)

WOO HOOO!!

Maybe we should call it FluxCapacitor.

Maybe it will only need 1.21 gigawatts to catch up to Bitshares.

450
General Discussion / Re: Introducing Cryptonomex International (CNI)
« on: February 22, 2016, 08:23:40 pm »
Very good news!  +5%

Pages: 1 ... 23 24 25 26 27 28 29 [30] 31 32 33 34 35 36 37 ... 168