...

I think most airdrops will end up with people who just dump their shares.  The airdrop needs an additional component that at least differentiates the people who care vs the people who will auto-dump.  If 80% of the people dump their shares, has the DAC gained value ? (rhetorical question)  At first I was more for the idea but as time has went on I've changed my opinion.  I like the idea of a random chance, but not one tied into purchases.  If there would be a way for a person to have to check to see fi they have received shares and not have them by default.  (That means they're at least slightly more motivated given that they're doing something with a possible outcome of 0..  vs guaranteed money given a typical airdrop) 

So Luckybit's suggestion is good in that it differentiates people who care, but it also is just another way of purchasing shares with a random component.  If you could find a way to actually discern motivated investors vs people who will just immediately dump then we'd have a solution.
...

Oh, I know why from the source code.
delegate will not  producing block when connection less than 5.

But why the connection is always 1 or 2? I have a public IP.

Quote from: alt on June 14, 2014, 06:31:53 am

I can't produce even 1 block after rebuild about 8hours ago.
the network and block sync seems no problem.
attention that  "wallet_seconds_until_next_block_production" is -5,

Code: [Select]

delegate (unlocked) >>> info
{
  "blockchain_head_block_num": 2929,
  "blockchain_head_block_time": "20140614T062800",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 35.780154924382146,
  "network_num_connections": 2,
  "wallet_unlocked_seconds_remaining": 99999835,
  "wallet_next_block_production_time": "20140614T062815",
  "wallet_seconds_until_next_block_production": -5,
  "wallet_local_time": "20140614T062820",
  "blockchain_random_seed": "8bb94b1e583370db1d9ed0e3e1c0ba8986812a78",
  "blockchain_shares": 9999979815269,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20170814T161215",
  "wallet_version": 100
}
delegate (unlocked)  >>> about
{
  "bitshares_toolkit_revision": "2079bad65120f1a3a04ee8abc0a0e7baa345b896",
  "bitshares_toolkit_revision_age": "8 hours ago",
  "fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
  "fc_revision_age": "32 hours ago",
  "compile_date": "compiled on Jun 14 2014 at 07:48:30"
}
my account is 17,18,19,20.
before this upgrade, I miss only 3 blocks.

I have one question.

I have latest build (pulled one hour ago from this post time)

I'm seeing following value:
 "blocks_produced": 0

But i see
"last_block_num_produced": 4294967295


So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.



Can someone explain this to me ?

Quote

djdexter (unlocked) >>> wallet_get_account djdexter-1
{
  "index": 4,
  "id": 301,
  "name": "djdexter-1",
  "public_data": null,
  "owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
  "active_key_history": [[
      "20140610T232300",
      "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
    ]
  ],
  "delegate_info": {
    "votes_for": 3000000,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 0,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140610T232300",
  "last_update": "20140610T232300",
  "meta_data": null,
  "account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
  "trust_level": 0,
  "private_data": null
}