Quote from: bytemaster on October 21, 2015, 01:51:21 pm

Lets just PAY them to view ads so they can pay their fees.

That is the basic idea. People who don't want to pay upfront can accept the freemium model and then everyone wins. We get people who have more money than attention and who do not have time to view ads, who will pay the fees or lifetime membership. We have people too poor which means they have more attention than money, so we can monetize their attention just like all the other free sites attempt to do.

Ads should be able to pay at least 20 cents an hour, at least 1 transaction an hour, 12 transactions a day,  or something reasonable like that. It ought to be enough money and it scales up if millions of users are involved.

Who is going to implement this and how ?
Who will embed ads and how much will it cost ?

(: I'll be shocked if it isn't better as mine is just a "restart if it crashes".

I will pull all the key switching stuff out and push a different script that just replays and resyncs in case of crash or low participation.  Hopefully tonight or tomorrow, but I'm getting married on Wednesday so things are a little hectic.

Congrats!

If we can ensure that all nodes return the same signing key with get_witness and every node has only 1 signing key this should mitigate the risk of signing on two forks.   Should be pretty easy to do add well.  What does everyone think?

In order to ensure this you need actual (direct) connectivity between your nodes.
In that case it is easier just to stop the primary and start the backup. You dont need to change signing keys.

added wackou to watch list, looks like they fixed their witness. I'll monitor their performance for 24 hours and vote again

What exactly do you monitor ?
If you need more diversity you may add my witness :
(get_witness emski
{
  "id": "1.6.36",
  "witness_account": "1.2.5568",
})

What I offer is acceptable performance, acceptable response rate (updates), sufficient hardware & bandwidth (at least for now), seed node (not sure why it wasn't included in default seed nodes) . Reference for this statement are my delegates record from bitshares 1.0 .

emski: emski
If I'm not late for the party ("id": "1.6.36")

Quote from: alt on October 16, 2015, 10:39:13 am

Quote from: iHashFury on October 16, 2015, 09:31:41 am

Can the new pull be disabled in the config?

I prefer a simple price feed. ( also I'm not an economist )

As a witness, you must understand the market engine. a bad parameter will break the peg.
All witness must publish these parameters,
My suggest is set short_squeeze_ratio between 1001 to 1100. this parameter is very important,
when it's 1100
SQP   = FEED / 1.1
when it's 1050
SQP = FEED /1.05

Quote from: bytemaster on October 15, 2015, 09:15:42 pm

A margin call will occur any time the highest bid is less than the CALL PRICE and greater than SQP

FEED = Settlement Price
SWAN = DEBT / COLLATERAL  - the point at which the network is insolvent.
CALL   = SWAN * 1.75
SQP   = FEED / 1.5

1.75 and 1.5 are specified as two parameters to the price feed. 

If you would like the feed to provide additional protection to the shorts, then ask the witnesses to adjust their feed publishing scripts to use SQP of FEED / 1.1.

Just beware that the consequence of protecting the shorts against thin markets is the following:

1. Shorts will end up posting less collateral
2. Greater dependence upon the feed vs the market
3. If there are no bids above the SQP price then margin will not get called even if the Feed Price is below the Call price.

Thanks for the info.
However I don't think this parameter should be DECIDED by witnesses, it's better to be set as a system parameter, and adjustable by committee proposals.

Witnesses should have no control over this parameter.