Well, so far everything is good.  Delegate & Windows Wallet Upgraded.  Dang!!  Wallet just seems to be getting better and better everytime.  Good job!!

Quote from: Empirical1 on August 21, 2014, 07:29:14 pm

I'm watching the little sell walls that there were on BTC38  BTSX/CNY get eaten up right now. It's just Buy, Buy, Buy...

Ripple is going down! 

Part of what we have to do (delegates and participants in the Bitshares community), is create demand.

For example I think we have to create on-ramps so people can actually acquire Bitshares. Minebitshares is one way but we need Gateways, ATMs, anything to help people get a taste of Bitshares X.

But we also have to think of ideas on how we can encourage people to never want to cash out. Having BitUSD with 5% interest will make it so people who want to protect their Bitcoin earnings can simply buy BitUSD5 from within BTER. That is one less reason to cash out.

If there are way more reasons for people to store their wealth in Bitshares, buy Bitshares, and few reasons to cash out beyond paying for upkeep, then few will cash out because there is more incentive/rationality in not doing so.

So if you like the direction the price is going one of the things I learned from other communities is it's a continuous effort to keep drumming up demand. The way to drum up demand is to increase the utility of Bitshares X or BitAssets. If you're running a business then you can offer a discount in people who pay you in BitGLD for instance. Stop accepting Bitcoin at a discount and give the discount to BitGLD.

yep, let people know all the BENEFITS.  A never-ending stream of benefits will win their hearts and minds!!
 

This is good product positioning.  Game Platform.  Great Idea.

Quote from: liondani on August 16, 2014, 12:29:33 pm

Quote from: bytemaster on August 16, 2014, 06:15:46 am

... you end up with a popularity contest but the problem is the most popular person or people might not be anything more than cult of personality. ...is popularity the only thing that matters for a delegate? ...

I agree with this.  I have seen delegate with 91% reliability with more approval than most others with better reliability and blocks produced.  Is the job to reliably produce blocks or to be a politician who is popular ?  Or maybe that is the question.  What is the job?  Based on all the discussion, time and energy spent on this, you would think the whole point of BitShares is to run and vote for delegates and the other "functionality" is an aside.

I would think that from a user standpoint, all this delegate and voting stuff is all back-office maintenance.  There should be some default vote for recommended slate of delegates or deault proxy for voting.  For example, I don't have the time or desire to participate in my homeowner's association much so I sign a proxy so that the current president can vote for me.

Quote from: emski on August 15, 2014, 07:19:27 am

I updated and everything seemed to work properly.
As soon as I published price feeds I started missing blocks.

Code: [Select]

emski (unlocked) >>> info
{
  "blockchain_head_block_num": 227738,
  "blockchain_head_block_age": "5 seconds old",
  "blockchain_head_block_timestamp": "2014-08-15T07:17:00",
  "blockchain_average_delegate_participation": "91.82 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "153,146.14196 BTSX",
  "blockchain_delegate_pay_rate": "1.26608 BTSX",
  "blockchain_share_supply": "1,999,957,225.95763 BTSX",
  "blockchain_blocks_left_in_round": 17,
  "blockchain_next_round_time": "3 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-15T07:19:50",
  "blockchain_random_seed": "14bfd263fd0987fa90ce853b16c3461e89f4524e",
  "client_data_dir": "/home/emski/bitsharesnodeTock/bitsharesx/programs/client/dd4.0",
  "network_num_connections": 66,
  "network_num_connections_max": 200,
  "ntp_time": "2014-08-15T07:17:05",
  "ntp_time_error": -0.0043769999999999998,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "37 minutes in the future",
  "wallet_unlocked_until_timestamp": "2014-08-15T07:53:41",
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "at least 3 minutes in the future",
  "wallet_next_block_production_timestamp": null
}
emski (unlocked) >>> blockchain_list_blocks
HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    TOTAL FEES      LATENCY PROCESSING TIME
===================================================================================================================
227738  2014-08-15T07:17:00 dpos.crazybit                   0       166     0.00000 BTSX    0       0.004883
227737  2014-08-15T07:16:50 fox                             0       166     0.00000 BTSX    0       0.000117
MISSED  2014-08-15T07:16:40 lotto-delegate                  N/A     N/A     N/A             N/A     N/A
227736  2014-08-15T07:16:30 init34                          0       166     0.00000 BTSX    0       0.002168

And where is my console.log ?


Output from 3.1 client:

Code: [Select]

     227736
     6b6301bb71de964c1a8f759f304316a3f6417967                lotto-delegate              2       502 2014-08-15T07:16:40         0      NO                  NO
     71f889b8659ff455185586ebedca7e99a21a59bf                           fox              0       166 2014-08-15T07:16:50         0     YES                 YES
         227744
     704bd508f16573c486e8ba828026f257364cc340               delegate.webber              0       166 2014-08-15T07:18:10         0     YES                  NO
     61d53df45eebe57e9f81632dc27eb845ced89d3e               delegate.webber              0       166 2014-08-15T07:18:10         0     YES                 YES
REASONS FOR INVALID BLOCKS
6b6301bb71de964c1a8f759f304316a3f6417967: 10 assert_exception: Assert Exception
converter_itr != _converters.end():
    {}
    th_a  operations.cpp:62 to_variant

    {}
    th_a  operations.cpp:64 to_variant

    {"trx_num":0}
    th_a  chain_database.cpp:1003 apply_transactions


Quote from: emski on August 15, 2014, 07:24:40 am

What if the delegate in the round just after me hasn't updated?
When we are required to publish price feeds?
Should we do it for all currencies ?

Quote from: Riverhead on August 15, 2014, 09:09:45 am

Not sure if this is related to 0.4.0 delegates vs 0.3.1 but I'm see this. Note that I haven't missed a block because of this. I have not published a feed yet.

Code: [Select]


Peer 104.131.134.181:51145 disconnected us: You offered us a block that we reject as invalid
Peer 106.185.24.234:39314 disconnected us: You offered us a block that we reject as invalid


Quote from: xeroc on August 15, 2014, 09:12:48 am

hm .. my backup system successfully upgraded and produced blocks .. when switching to the main system with 0.4.0 he missed blocks ... wlthough all seemed fine ..
strange .. looking into ito

//edit: seems I needed to reanble block production

Do not publish price feeds until after hardfork and all clients are upgraded. This is a new operation that is part of the hardfork. All old clients will reject blocks containing publish price feed operation. This is the reason for missed blocks.

Large transaction and block sizes are also part of the hardfork, and could result in missed blocks.

console.log was disabled by default in previous update for security concerns. It can be enabled using --log-commands argument.

Delegates are still free to upgrade but must be aware that there a crashing issue has been identified. Brave delegates can upgrade and run client in a debugger to help us get a stack trace of the crash.

ah, great. 

The Unwittingly Brave

if you have a delegate running then you should update .. at the end everything is running fine .. at least at my end

what about price feeds?  Don't see any crystal clear instructions on that.

Do the opposite of what I do and you will be just fine...

I like this.    This is how I try to think now...so i try to do the opposite of my initial instinct (proven bad by past results) So far, it seems to have worked better.  Hard to make sure that you get the first wrong approach though, so you can then plan the opposite. 

Based on that approach I also now (not my first instinct!) favor the whales and mass market approach to marketing for BitShares!

George Costanza's Opposite Theory: https://www.youtube.com/watch?v=cKUvKE3bQlY


(fingers crossed)

BTSX needs momentum; market cap is how the avalanche will start.

BTC is what it is today not because of social media presence, trendy ads, political lobbying or clever P2P marketing.

BTC is what it is because there are a few very powerful and connected hands pulling the strings.

We need a few whales, not a bunch of minnows.

I3/Brian are doing this right.

You may be right about this...I'm curious as to whom you think the few very powerful and connected are that have been pulling the strings for BTC?