Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS33.27%
Net Worth
0.218USD
STEEM
0.007STEEM
SBD
0.038SBD
Effective Power
5.001SP
├── Own SP
3.677SP
└── Incoming Deleg
+1.324SP

Detailed Balance

STEEM
balance
0.007STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
3.677SP
Delegated Out
0.000SP
Delegation In
1.324SP
Effective Power
5.001SP
Reward SP (pending)
0.000SP
SBD
sbd_balance
0.038SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.000SBD
{
  "balance": "0.007 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.000 STEEM",
  "vesting_shares": "5987.209460 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "2156.450346 VESTS",
  "sbd_balance": "0.038 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

namealwaysnew
id520426
rank980,397
reputation8430473615
created2017-12-22T16:24:18
recovery_accountsteem
proxyNone
post_count875
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2020-02-10T21:49:09
last_root_post2020-02-10T21:49:09
last_vote_time2019-10-02T12:01:12
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.007 STEEM
savings_balance0.000 STEEM
sbd_balance0.038 SBD
savings_sbd_balance0.000 SBD
vesting_shares5987.209460 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares2156.450346 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update2019-11-20T21:20:36
minedNo
sbd_seconds181,669,920
sbd_last_interest_payment2019-03-05T15:54:54
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 520426,
  "name": "alwaysnew",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5hGLySo5rX3oJdLVudTGhot9VVqEiLJbMKYrafuWLE5hrmGKQG",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM68nwjBagTPuxWn3QgkRa93uc4ejAtiyr1ATRY7gKqqcmAyTfxg",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [
      [
        "dlike.app",
        1
      ],
      [
        "smartsteem",
        1
      ],
      [
        "steemhunt.com",
        1
      ]
    ],
    "key_auths": [
      [
        "STM6KJznVSC1SehjDSw62ATr5SSE63fLZgiA2cShL1YEnDHNukYjE",
        1
      ]
    ]
  },
  "memo_key": "STM8fc7RBGoh9P6FcdrTG12PJoxKrtyjQAEbsuJ8iC13bRBk9A7ny",
  "json_metadata": "{\"profile\":{\"profile_image\":\"http://www4.0zz0.com/2017/12/22/22/566536215.jpg\",\"cover_image\":\"http://www4.0zz0.com/2017/12/22/22/566536215.jpg\",\"dtube_pub\":\"wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo\"}}",
  "posting_json_metadata": "{\"profile\":{\"profile_image\":\"http://www4.0zz0.com/2017/12/22/22/566536215.jpg\",\"cover_image\":\"http://www4.0zz0.com/2017/12/22/22/566536215.jpg\",\"dtube_pub\":\"wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo\"}}",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "2019-11-20T21:20:36",
  "created": "2017-12-22T16:24:18",
  "mined": false,
  "recovery_account": "steem",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 875,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779052527
  },
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779052527
  },
  "voting_power": 0,
  "balance": "0.007 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.038 SBD",
  "sbd_seconds": "181669920",
  "sbd_seconds_last_update": "2019-03-21T00:15:54",
  "sbd_last_interest_payment": "2019-03-05T15:54:54",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "0.000 STEEM",
  "reward_vesting_balance": "0.000000 VESTS",
  "reward_vesting_steem": "0.000 STEEM",
  "vesting_shares": "5987.209460 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "2156.450346 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "curation_rewards": 12,
  "posting_rewards": 1322,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2020-02-10T21:49:09",
  "last_root_post": "2020-02-10T21:49:09",
  "last_vote_time": "2019-10-02T12:01:12",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": "8430473615",
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 980397
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 1.324 SP to @alwaysnew
2026/05/17 21:15:27
delegatorsteem
delegateealwaysnew
vesting shares2156.450346 VESTS
Transaction InfoBlock #106139868/Trx eaf7fd9ad42a9ac1d557aa3937fe213dba725a8d
View Raw JSON Data
{
  "trx_id": "eaf7fd9ad42a9ac1d557aa3937fe213dba725a8d",
  "block": 106139868,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-17T21:15:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "2156.450346 VESTS"
    }
  ]
}
steemdelegated 1.001 SP to @alwaysnew
2026/05/11 17:22:45
delegatorsteem
delegateealwaysnew
vesting shares1629.434820 VESTS
Transaction InfoBlock #105963193/Trx 3f6852542b7a0a25481eedd3e031ed0c8c6ac4f8
View Raw JSON Data
{
  "trx_id": "3f6852542b7a0a25481eedd3e031ed0c8c6ac4f8",
  "block": 105963193,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-11T17:22:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "1629.434820 VESTS"
    }
  ]
}
steemdelegated 1.332 SP to @alwaysnew
2026/04/25 20:41:06
delegatorsteem
delegateealwaysnew
vesting shares2168.966102 VESTS
Transaction InfoBlock #105507608/Trx f3acc38c62c311983bde5eeeb4e53b8d30777306
View Raw JSON Data
{
  "trx_id": "f3acc38c62c311983bde5eeeb4e53b8d30777306",
  "block": 105507608,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-25T20:41:06",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "2168.966102 VESTS"
    }
  ]
}
steemdelegated 1.070 SP to @alwaysnew
2023/11/13 10:56:03
delegatorsteem
delegateealwaysnew
vesting shares1741.904685 VESTS
Transaction InfoBlock #79842976/Trx cecad301d3533392e8e311f7d94a8773258ee74d
View Raw JSON Data
{
  "trx_id": "cecad301d3533392e8e311f7d94a8773258ee74d",
  "block": 79842976,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-13T10:56:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "1741.904685 VESTS"
    }
  ]
}
steemdelegated 1.693 SP to @alwaysnew
2023/09/21 18:18:51
delegatorsteem
delegateealwaysnew
vesting shares2756.418275 VESTS
Transaction InfoBlock #78343629/Trx 1806c5d2b1a77c7324e22b385604fba99941f794
View Raw JSON Data
{
  "trx_id": "1806c5d2b1a77c7324e22b385604fba99941f794",
  "block": 78343629,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-21T18:18:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "2756.418275 VESTS"
    }
  ]
}
steemdelegated 1.829 SP to @alwaysnew
2022/11/03 08:31:21
delegatorsteem
delegateealwaysnew
vesting shares2978.099713 VESTS
Transaction InfoBlock #69109461/Trx f8610ddac50ff45e0853501c169c2b7ff8baf0eb
View Raw JSON Data
{
  "trx_id": "f8610ddac50ff45e0853501c169c2b7ff8baf0eb",
  "block": 69109461,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T08:31:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "2978.099713 VESTS"
    }
  ]
}
ph-supportsent 0.001 STEEM to @alwaysnew
2022/08/16 11:57:00
fromph-support
toalwaysnew
amount0.001 STEEM
memo
Transaction InfoBlock #66852478/Trx 65d2ed58de4dabbbab0fb6ab016dd2de39ec35c0
View Raw JSON Data
{
  "trx_id": "65d2ed58de4dabbbab0fb6ab016dd2de39ec35c0",
  "block": 66852478,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-08-16T11:57:00",
  "op": [
    "transfer",
    {
      "from": "ph-support",
      "to": "alwaysnew",
      "amount": "0.001 STEEM",
      "memo": ""
    }
  ]
}
steemdelegated 1.964 SP to @alwaysnew
2022/01/17 08:04:06
delegatorsteem
delegateealwaysnew
vesting shares3198.632944 VESTS
Transaction InfoBlock #60805970/Trx bb54c9e8a9e36b7276e0e8d0f9b3fd7c452b4437
View Raw JSON Data
{
  "trx_id": "bb54c9e8a9e36b7276e0e8d0f9b3fd7c452b4437",
  "block": 60805970,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T08:04:06",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "3198.632944 VESTS"
    }
  ]
}
steemdelegated 2.077 SP to @alwaysnew
2021/06/13 22:06:30
delegatorsteem
delegateealwaysnew
vesting shares3382.401602 VESTS
Transaction InfoBlock #54604503/Trx 6b6676263e3cb517f3d8367028d36b588422969b
View Raw JSON Data
{
  "trx_id": "6b6676263e3cb517f3d8367028d36b588422969b",
  "block": 54604503,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-13T22:06:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "3382.401602 VESTS"
    }
  ]
}
steemdelegated 2.192 SP to @alwaysnew
2020/12/11 08:29:18
delegatorsteem
delegateealwaysnew
vesting shares3569.823576 VESTS
Transaction InfoBlock #49352071/Trx 73e80e338e702131a1cc5420153558bbee80cc57
View Raw JSON Data
{
  "trx_id": "73e80e338e702131a1cc5420153558bbee80cc57",
  "block": 49352071,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T08:29:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "3569.823576 VESTS"
    }
  ]
}
steemdelegated 1.174 SP to @alwaysnew
2020/12/06 02:06:51
delegatorsteem
delegateealwaysnew
vesting shares1912.543513 VESTS
Transaction InfoBlock #49203642/Trx d1838fffbcd67720e73cea01349ceba764798d4b
View Raw JSON Data
{
  "trx_id": "d1838fffbcd67720e73cea01349ceba764798d4b",
  "block": 49203642,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T02:06:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}
steemdelegated 2.202 SP to @alwaysnew
2020/11/27 01:59:39
delegatorsteem
delegateealwaysnew
vesting shares3585.338526 VESTS
Transaction InfoBlock #48948196/Trx 3e4cfee87e35cbcf945f79e9248891c5c0825534
View Raw JSON Data
{
  "trx_id": "3e4cfee87e35cbcf945f79e9248891c5c0825534",
  "block": 48948196,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-27T01:59:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "3585.338526 VESTS"
    }
  ]
}
steemdelegated 2.320 SP to @alwaysnew
2020/05/11 22:23:27
delegatorsteem
delegateealwaysnew
vesting shares3777.160586 VESTS
Transaction InfoBlock #43292835/Trx c39740ea681099ed358983e0f693dcbff030a3b5
View Raw JSON Data
{
  "trx_id": "c39740ea681099ed358983e0f693dcbff030a3b5",
  "block": 43292835,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-11T22:23:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "3777.160586 VESTS"
    }
  ]
}
steemdelegated 16.154 SP to @alwaysnew
2020/05/09 03:01:33
delegatorsteem
delegateealwaysnew
vesting shares26304.534018 VESTS
Transaction InfoBlock #43213854/Trx 0152be290e7d02bdef224c76685cb847cb59820b
View Raw JSON Data
{
  "trx_id": "0152be290e7d02bdef224c76685cb847cb59820b",
  "block": 43213854,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T03:01:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "26304.534018 VESTS"
    }
  ]
}
steemdelegated 1.760 SP to @alwaysnew
2020/05/08 06:12:54
delegatorsteem
delegateealwaysnew
vesting shares2866.328691 VESTS
Transaction InfoBlock #43189467/Trx 1c0c6f015f9d95bf1463070df2b5a447810e696b
View Raw JSON Data
{
  "trx_id": "1c0c6f015f9d95bf1463070df2b5a447810e696b",
  "block": 43189467,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T06:12:54",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "2866.328691 VESTS"
    }
  ]
}
steemdelegated 16.170 SP to @alwaysnew
2020/04/23 14:45:00
delegatorsteem
delegateealwaysnew
vesting shares26330.850204 VESTS
Transaction InfoBlock #42778273/Trx 610e1824fce749de28fb9f9abfff492b0d4cff88
View Raw JSON Data
{
  "trx_id": "610e1824fce749de28fb9f9abfff492b0d4cff88",
  "block": 42778273,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-23T14:45:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "26330.850204 VESTS"
    }
  ]
}
alwaysnewcustom json: community
2020/04/16 22:57:00
required auths[]
required posting auths["alwaysnew"]
idcommunity
json["subscribe",{"community":"hive-196037"}]
Transaction InfoBlock #42591959/Trx 226782f4f34c526ba98f101c70ae449b667643cb
View Raw JSON Data
{
  "trx_id": "226782f4f34c526ba98f101c70ae449b667643cb",
  "block": 42591959,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T22:57:00",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "alwaysnew"
      ],
      "id": "community",
      "json": "[\"subscribe\",{\"community\":\"hive-196037\"}]"
    }
  ]
}
alwaysnewcustom json: community
2020/03/23 22:06:24
required auths[]
required posting auths["alwaysnew"]
idcommunity
json["subscribe",{"community":"hive-101145"}]
Transaction InfoBlock #41913218/Trx cc3575118dd9ff936a37746f1a2b80b88012118f
View Raw JSON Data
{
  "trx_id": "cc3575118dd9ff936a37746f1a2b80b88012118f",
  "block": 41913218,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-23T22:06:24",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "alwaysnew"
      ],
      "id": "community",
      "json": "[\"subscribe\",{\"community\":\"hive-101145\"}]"
    }
  ]
}
beemenginesent 0.001 STEEM to @alwaysnew- "💎 Awesome Community Offer, Your Best STEEM Companion, automated 24/24 boosting your posts, guaranteed community extra votes, passive curation earnings and more, checkout https://www.steembeem.com 🤙 ..."
2020/02/10 21:50:18
frombeemengine
toalwaysnew
amount0.001 STEEM
memo💎 Awesome Community Offer, Your Best STEEM Companion, automated 24/24 boosting your posts, guaranteed community extra votes, passive curation earnings and more, checkout https://www.steembeem.com 🤙 or join in for one month by sending ONLY 1 STEEM 🤯 to @beemengine with memo: subscribe
Transaction InfoBlock #40708177/Trx ca8c50390a35dbd9ef68696d0910b62e2f62aeb8
View Raw JSON Data
{
  "trx_id": "ca8c50390a35dbd9ef68696d0910b62e2f62aeb8",
  "block": 40708177,
  "trx_in_block": 27,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-02-10T21:50:18",
  "op": [
    "transfer",
    {
      "from": "beemengine",
      "to": "alwaysnew",
      "amount": "0.001 STEEM",
      "memo": "💎 Awesome Community Offer, Your Best STEEM Companion, automated 24/24 boosting your posts, guaranteed community extra votes, passive curation earnings and more, checkout https://www.steembeem.com 🤙 or join in for one month by sending ONLY 1 STEEM 🤯 to @beemengine with memo: subscribe"
    }
  ]
}
2020/02/10 21:49:09
parent author
parent permlinkbitcoin
authoralwaysnew
permlinktaproot-graftroot-to-the-bitcoin-development-mailing-list
titletaproot/graftroot to the #bitcoin development mailing list.
body[bitcoin-dev] Taproot (and graftroot) complexity Bryan Bishop kanzure at gmail.com Sun Feb 9 20:19:55 UTC 2020 Previous message: [bitcoin-dev] Purge attacks (spin on sabotage attacks) Next message: [bitcoin-dev] An alternative deployment path for taproot technology (Re: Taproot (and graftroot) complexity) Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] The following is a message forwarded from an anonymous email that, for whatever reason, couldn't be relayed through the mailing list without my assistance. This email is the first of a collection of sentiments from a group of developers who in aggregate prefer to remain anonymous. These emails have been sent under a pseudonym so as to keep the focus of discussion on the merits of the technical issues, rather than miring the discussion in personal politics. Our goal isn't to cause a schism, but rather to help figure out what the path forward is with Taproot. To that end, we: 1) Discuss the merits of Taproot's design versus simpler alternatives (see thread subject, "Taproot (and Graftroot) Complexity"). 2) Propose an alternative path to deploying the technologies described in BIP-340, BIP-341, and BIP-342 (see thread subject, "An Alternative Deployment Path for Taproot Technologies"). 3) Suggest a modification to Taproot to reduce some of the overhead (see thread subject, "Taproot Public NUMS Optimization"). Now that the BIP has moved to draft we felt that now was the time to prioritize review to make sure it was an acceptable change for our activities. As a group, we're excited about the totality of what Taproot has to offer. However, after our review, we're left perplexed about the development of Taproot (and Graftroot, to a lesser extent). We also want to convey that we have nothing but respect for the developers and community who have poured their heart and soul into preparing Taproot. Self evidently, it is an impressive synthesis of ideas. We believe that the highest form of respect to pay such a synthesis of ideas is a detailed and critical review, as it's pertinent to closely consider changes to Bitcoin. In essence, Taproot is fundamentally the same as doing https://github.com/bitcoin/bips/blob/master/bip-0114.mediawiki and Schnorr signatures separately. The main reason for putting them together -- as mentioned in the BIP -- is a gain in efficiency. But this efficiency pre-supposes a specific use case and probability distribution of use cases. Compare: Suppose a MAST for {a,b,c,d,e,f,g,h} spending conditions it looks something like this: /\ / \ / \ / \ /\ /\ / \ / \ /\ /\ /\ /\ a b c d e f g h If we want this to be functionally equivalent to Taproot, we add a new path: /\ /\ / \ / \ / \ /\ /\ / \ / \ /\ /\ /\ /\ a b c d e f g h Now, to spend from this MBV you have to reveal 32 bytes on the stack for the not taken branch, and 35 bytes for the schnorr_checksig (1 byte push, 33 bytes PK, 1 byte checksig). This is 67 bytes more than Taproot would require for the same spending condition. However, suppose we wanted to use one of the script paths instead. We still need to have one extra hash for the schnorr_checksig} (depending on if we put the key in this position or not--see below). But now we can spend with just a logarithmic control program path. However, if we do the same script via taproot, we now need to provide the base public key (33 bytes) as well as the root hash (32 bytes) and path and then the actual scripts. With the need for 2 push bytes, this ends up being back at 67 bytes extra. Is Taproot just a probability assumption about the frequency and likelihood of the signature case over the script case? Is this a good assumption? The BIP only goes as far as to claim that the advantage is apparent if the outputs *could be spent* as an N of N, but doesn't make representations about how likely that N of N case would be in practice compared to the script paths. Perhaps among use cases, more than half of the ones we expect people to be doing could be spent as an N of N. But how frequently would that path get used? Further, while the *use cases* might skew toward things with N of N opt-out, we might end up in a power law case where it's the one case that doesn't use an N of N opt out at all (or at a de minimis level) that becomes very popular, thereby making Taproot more costly then beneficial. Further, if you don't want to use a Taproot top-level key (e.g., you need to be able to audit that no one can spend outside of one of the script conditions), then you need to use a NUMS (nothing up my sleeve) point. This forces users who don't want Taproot to pay the expense, when if they just had a MAST based witness type they would be cheaper. So if this use case is at all common, Taproot leaves them worse off in terms of fees. Given that script paths are usually done in the case where there is some contested close, it's actually in the interest of protocol developers that the contested script path be as efficient as possible so that the fees paid maximally increase the feerate. We think this can be fixed simply in Taproot though, as noted below. On privacy, we're also a bit confused as to the goal of Taproot over MAST and Schnorr. Earlier, we presented a design with MAST which is very close to Taproot. However, it'd also be possible to just add schnorr_checksig} to the set {a,b,c,d,e,f,g,h}, shuffle them, and compute some MAST structure (perhaps probability encoded) on them. This has the effect of not having much additional fees for adding the extra Schnorr path at redeem time (only 1 extra branch on 2/8 script paths), e.g. /\ / \ / \ / \ /\ /\ / \ / \ /\ /\ /\ /\ a b c d e f/\ g h We could argue that this is more private than Taproot, because we don't distinguish between the Schnorr key case and other cases by default, so chain analyzers can't tell if the signature came from the Taproot case or from one of the Script paths. There's also no NUMS point required, which means chain analyzers can't tell when you spend that there was no top level key if the NUMS point is not per-output indistinguishable. By using a semi-randomized MAST structure, chain analyzers also can't tell exactly how big your spend condition MAST was. In particular, you care more about privacy when you are contesting a close of a channel or other script path because then the miners could be more likely to extract a rent from you as "ransom" for properly closing your channel (or in other words, in a contested close the value of the closing transaction is larger than usual). It would also be possible to do something really simple which is to allow the witness type to be either a MAST hash OR a schnorr key (but not a Taproot). This allows you to not completely fracture the anonymity set between people who want plain Schnorr and people who want MAST (at least until they go to spend). This fix can also be used in Taproot in place of a NUMS point, to decrease extra fees. It's unclear if this plays negatively with any future batch validation mechanism though, but the contextual checks to exclude a witness program from the batch are relatively simple. See thread subject, "Taproot Public NUMS Optimization". The considerations around Graftroot, a proposed delegation mechanism, is a bit similar. Delegation is a mechanism by which a UTXO with script S can sign a script R which can then be executed in addition to S without requiring a transaction. This allows an output to monotonically and dynamically increase the number of conditions under which it can be spent. As noted by Pieter Wiulle here: ://github.com/kanzure/diyhpluswiki/commit/a03f6567d714f8733b578de263a4b149441cd058 delegation was originally possible in Bitcoin, but got broken during an emergency fork to split the scriptSig and scriptpubkey separation. Rather than adding some fancy delegation mechanism in Bitcoin, why not just have a P2SH-like semantic which allows a delegated script to be evaluated? See BIP-117 ://github.com/bitcoin/bips/blob/master/bip-0117.mediawiki. This way we aren't special casing where delegation can occur, and we can allow taproot nested spending conditions (i.e., with timelocks) to generate their own delegations. As I've seen Graftroot discussed thus far, it is as a top-level witness program version like Taproot and non-recursive. Similar to the above discussion, top-level is more efficient if you suspect that delegation will be most likely occurring at the top level, but it's not clear that's a good assumption as it may be common to want to allow different scripts to delegate. Overall, we are left with concerns both about the merit of doing Taproot versus alternatives, as well as the process through which we got to be here. 1) Is Taproot actually more private than bare MAST and Schnorr separately? What are the actual anonymity set benefits compared to doing the separately? 2) Is Taproot actually cheaper than bare MAST and Schnorr separately? What evidence do we have that the assumption it will be more common to use Taproot with a key will outweigh Script cases? 3) Is Taproot riskier than bare MAST and Schnorr separately given the new crypto? How well reviewed is the actual crypto parts? None of us personally feel comfortable reviewing the crypto in Schnorr -- what's the set of people who have thoroughly reviewed the crypto and aren't just ACKing because they trust other developers to have looked at it close enough? 4) Design wise, couldn't we forego the NUMS point requirement and be able to check if it's a hash root directly? This would encumber users who don't need the key path a cheaper spend path. See thread subject, "Taproot Public NUMS Optimization". 5) Is the development model of trying to jam a bunch of features into Bitcoin all at once good for Bitcoin development? Would we be better off if we embraced incremental improvements that can work together (e.g., MAST and then Schnorr)? Although the BIP raises some points about anonymity sets being why to do them all at once, it's not clear to me this argument holds water (same goes for businesses not upgrading). If we can take things as smaller steps, we are not only more secure, but we also have more time to dedicate review to each change independently. We also end up co-mingling changes that people end up accepting only because they want one and they're bundled (e.g., MAST and Schnorr, MAST seems like a much less risky addition versus Schnorr). See thread subject, "An Alternative Deployment Path for Taproot Technologies". Our provocation with this email is primarily that we think we should more carefully consider the benefits of Taproot over simpler primitives that are not only easier to review, but could have been made available much sooner rather than waiting on putting everything all together for an unclear aggregate benefit. We do think that most of the developers have been honest about the benefits of Taproot, but that on closer look we feel the general ecosystem has oversold Taproot as being the key enabler for a collection of techniques that we could do with much simpler building blocks. At the end of the day, we do not strongly advocate not deploying Taproot at this point in the review cycle. We think the Taproot Public NUMS Optimization may be a good idea, worth considering if it's not insecure, as it cuts through the case where you would otherwise need a NUMS point. Things like TapScript and its MAST mechanisms are well designed and offer exciting new deployment paths, and would be something we would use even if we opted for MAST instead of Taproot. However, we also believe it is our duty to raise these concerns and suggestions, and we look forward to listening to the responses of the community. Great thanks, The Group SUBJECT: An Alternative Deployment Path for Taproot Technologies This email is the second of a collection of sentiments from a group of developers who in aggregate prefer to remain anonymous. These emails have been sent under a pseudonym so as to keep the focus of discussion on the merits of the technical issues, rather than miring the discussion in personal politics. Our goal isn't to cause a schism, but rather to help figure out what the path forward is with Taproot. To that end, we: 1) Discuss the merits of Taproot's design versus simpler alternatives (see thread subject, "Taproot (and Graftroot) Complexity"). 2) Propose an alternative path to deploying the technologies described in BIP-340, BIP-341, and BIP-342 (see thread subject, "An Alternative Deployment Path for Taproot Technologies"). 3) Suggest a modification to Taproot to reduce some of the overhead (see thread subject, "Taproot Public NUMS Optimization"). As a follow up to our prior message, we propose a different path forward for the Taproot family of changes: 1) A separate soft-fork for Merkle Branch Witnesses based on Taproot; 2) A separate soft-fork for Schnorr Signatures 3) A separate follow up soft-fork which enables Taproot and Graftroot We think that the first 2 forks can be offered at the same time or one at a time. Taproot, as a follow up to changes 1 and 2, can be enabled as a soft-fork on the existing semantics, but requiring a new witness version. With the Public NUMS Optimization, wallets could upgrade by just changing one version byte to be in the same anonymity set as Taproot. It's not clear to us that the time to prepare a BIP and implementation for 1 and 2 at this point would be any less than the time to do Taproot as currently proposed. However, we believe that such a deployment plan is a reasonable option as it is more conservative, as Merkle Branch witnesses are relatively simple and users only have to use Schnorr signing if they want to, and can otherwise continue to use ECDSA. A further benefit of waiting on 3 is that we get to collect real world protocol engineering experience to see how frequently the Taproot frequency of use assumption holds, and if it is worth doing or not. Great thanks, The Group -- - Bryan ://heybryan.org/ 1 512 203 0507 -------------- next part -------------- An attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20200209/94a71b6f/attachment-0001.html> Previous message: [bitcoin-dev] Purge attacks (spin on sabotage attacks) Next message: [bitcoin-dev] An alternative deployment path for taproot technology (Re: Taproot (and graftroot) complexity) Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the bitcoin-dev mailing list ://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-February/017615.html
json metadata{"tags":["bitcoin"],"links":["https://github.com/bitcoin/bips/blob/master/bip-0114.mediawiki","http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20200209/94a71b6f/attachment-0001.html"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #40708154/Trx 2dc54e353c75d027e4541385a2ef852684529b6e
View Raw JSON Data
{
  "trx_id": "2dc54e353c75d027e4541385a2ef852684529b6e",
  "block": 40708154,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-02-10T21:49:09",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "bitcoin",
      "author": "alwaysnew",
      "permlink": "taproot-graftroot-to-the-bitcoin-development-mailing-list",
      "title": "taproot/graftroot to the #bitcoin development mailing list.",
      "body": "[bitcoin-dev] Taproot (and graftroot) complexity\nBryan Bishop kanzure at gmail.com\nSun Feb 9 20:19:55 UTC 2020\nPrevious message: [bitcoin-dev] Purge attacks (spin on sabotage attacks)\nNext message: [bitcoin-dev] An alternative deployment path for taproot technology (Re: Taproot (and graftroot) complexity)\nMessages sorted by: [ date ] [ thread ] [ subject ] [ author ]\nThe following is a message forwarded from an anonymous email that, for\nwhatever reason, couldn't be relayed through the mailing list without my\nassistance.\n\nThis email is the first of a collection of sentiments from a group of\ndevelopers\nwho in aggregate prefer to remain anonymous. These emails have been sent\nunder a\npseudonym so as to keep the focus of discussion on the merits of the\ntechnical\nissues, rather than miring the discussion in personal politics. Our goal\nisn't\nto cause a schism, but rather to help figure out what the path forward is\nwith\nTaproot. To that end, we:\n\n1) Discuss the merits of Taproot's design versus simpler alternatives (see\nthread subject, \"Taproot (and Graftroot) Complexity\").\n2) Propose an alternative path to deploying the technologies described in\nBIP-340, BIP-341, and BIP-342 (see thread subject, \"An Alternative\nDeployment\nPath for Taproot Technologies\").\n3) Suggest a modification to Taproot to reduce some of the overhead (see\nthread\nsubject, \"Taproot Public NUMS Optimization\").\n\nNow that the BIP has moved to draft we felt that now was the time to\nprioritize\nreview to make sure it was an acceptable change for our activities. As a\ngroup,\nwe're excited about the totality of what Taproot has to offer. However,\nafter\nour review, we're left perplexed about the development of Taproot (and\nGraftroot, to a lesser extent).\n\nWe also want to convey that we have nothing but respect for the developers\nand\ncommunity who have poured their heart and soul into preparing Taproot. Self\nevidently, it is an impressive synthesis of ideas. We believe that the\nhighest\nform of respect to pay such a synthesis of ideas is a detailed and critical\nreview, as it's pertinent to closely consider changes to Bitcoin.\n\n\nIn essence, Taproot is fundamentally the same as doing\nhttps://github.com/bitcoin/bips/blob/master/bip-0114.mediawiki and Schnorr\nsignatures separately.\n\nThe main reason for putting them together -- as mentioned in the BIP -- is a\ngain in efficiency. But this efficiency pre-supposes a specific use case and\nprobability distribution of use cases.\n\nCompare:\n\nSuppose a MAST for {a,b,c,d,e,f,g,h} spending conditions it looks something\nlike this:\n\n      /\\\n     /  \\\n    /    \\\n   /      \\\n  /\\      /\\\n /  \\    /  \\\n/\\  /\\  /\\  /\\\na b c d e f g h\n\nIf we want this to be functionally equivalent to Taproot, we add a new path:\n\n       /\\\n      /\\ \n     /  \\\n    /    \\\n   /      \\\n  /\\      /\\\n /  \\    /  \\\n/\\  /\\  /\\  /\\\na b c d e f g h\n\nNow, to spend from this MBV you have to reveal 32 bytes on the stack for\nthe not\ntaken branch, and 35 bytes for the  schnorr_checksig (1 byte push, 33\nbytes\nPK, 1 byte checksig).\n\nThis is 67 bytes more than Taproot would require for the same spending\ncondition.\n\nHowever, suppose we wanted to use one of the script paths instead. We still\nneed\nto have one extra hash for the  schnorr_checksig} (depending on if we\nput\nthe key in this position or not--see below). But now we can spend with just\na\nlogarithmic control program path.\n\nHowever, if we do the same script via taproot, we now need to provide the\nbase\npublic key (33 bytes) as well as the root hash (32 bytes) and path and then\nthe\nactual scripts. With the need for 2 push bytes, this ends up being back at\n67\nbytes extra.\n\nIs Taproot just a probability assumption about the frequency and likelihood\nof\nthe signature case over the script case? Is this a good assumption?  The BIP\nonly goes as far as to claim that the advantage is apparent if the outputs\n*could be spent* as an N of N, but doesn't make representations about how\nlikely\nthat N of N case would be in practice compared to the script paths. Perhaps\namong use cases, more than half of the ones we expect people to be doing\ncould be\nspent as an N of N. But how frequently would that path get used? Further,\nwhile\nthe *use cases* might skew toward things with N of N opt-out, we might end\nup in\na power law case where it's the one case that doesn't use an N of N opt out\nat\nall (or at a de minimis level) that becomes very popular, thereby making\nTaproot\nmore costly then beneficial.\n\nFurther, if you don't want to use a Taproot top-level key (e.g., you need\nto be\nable to audit that no one can spend outside of one of the script\nconditions),\nthen you need to use a NUMS (nothing up my sleeve) point. This forces users\nwho\ndon't want Taproot to pay the expense, when if they just had a MAST based\nwitness type they would be cheaper. So if this use case is at all common,\nTaproot leaves them worse off in terms of fees. Given that script paths are\nusually done in the case where there is some contested close, it's actually\nin\nthe interest of protocol developers that the contested script path be as\nefficient as possible so that the fees paid maximally increase the feerate.\nWe\nthink this can be fixed simply in Taproot though, as noted below.\n\n\n\nOn privacy, we're also a bit confused as to the goal of Taproot over MAST\nand\nSchnorr. Earlier, we presented a design with MAST which is very close to\nTaproot.\nHowever, it'd also be possible to just add schnorr_checksig} to the\nset\n{a,b,c,d,e,f,g,h}, shuffle them, and compute some MAST structure (perhaps\nprobability encoded) on them. This has the effect of not having much\nadditional\nfees for adding the extra Schnorr path at redeem time (only 1 extra branch\non\n2/8 script paths), e.g.\n\n      /\\\n     /  \\\n    /    \\\n   /      \\\n  /\\      /\\\n /  \\    /  \\\n/\\  /\\  /\\  /\\\na b c d e f/\\\n          g  h\n\nWe could argue that this is more private than Taproot, because we don't\ndistinguish between the Schnorr key case and other cases by default, so\nchain\nanalyzers can't tell if the signature came from the Taproot case or from\none of\nthe Script paths. There's also no NUMS point required, which means chain\nanalyzers can't tell when you spend that there was no top level key if the\nNUMS\npoint is not per-output indistinguishable. By using a semi-randomized MAST\nstructure, chain analyzers also can't tell exactly how big your spend\ncondition\nMAST was. In particular, you care more about privacy when you are\ncontesting a\nclose of a channel or other script path because then the miners could be\nmore\nlikely to extract a rent from you as \"ransom\" for properly closing your\nchannel\n(or in other words, in a contested close the value of the closing\ntransaction is\nlarger than usual).\n\nIt would also be possible to do something really simple which is to allow\nthe\nwitness type to be either a MAST hash OR a schnorr key (but not a Taproot).\nThis\nallows you to not completely fracture the anonymity set between people who\nwant\nplain Schnorr and people who want MAST (at least until they go to spend).\nThis\nfix can also be used in Taproot in place of a NUMS point, to decrease extra\nfees. It's unclear if this plays negatively with any future batch validation\nmechanism though, but the contextual checks to exclude a witness program\nfrom\nthe batch are relatively simple. See thread subject, \"Taproot Public NUMS\nOptimization\".\n\nThe considerations around Graftroot, a proposed delegation mechanism, is a\nbit\nsimilar. Delegation is a mechanism by which a UTXO with script S can sign a\nscript R which can then be executed in addition to S without requiring a\ntransaction. This allows an output to monotonically and dynamically\nincrease the\nnumber of conditions under which it can be spent. As noted by Pieter Wiulle\nhere:\n://github.com/kanzure/diyhpluswiki/commit/a03f6567d714f8733b578de263a4b149441cd058\ndelegation was originally possible in Bitcoin, but got broken during an\nemergency fork to split the scriptSig and scriptpubkey separation. Rather\nthan\nadding some fancy delegation mechanism in Bitcoin, why not just have a\nP2SH-like\nsemantic which allows a delegated script to be evaluated? See BIP-117\n://github.com/bitcoin/bips/blob/master/bip-0117.mediawiki. This way we\naren't special casing where delegation can occur, and we can allow taproot\nnested spending conditions (i.e., with timelocks) to generate their own\ndelegations. As I've seen Graftroot discussed thus far, it is as a top-level\nwitness program version like Taproot and non-recursive. Similar to the above\ndiscussion, top-level is more efficient if you suspect that delegation will\nbe\nmost likely occurring at the top level, but it's not clear that's a good\nassumption as it may be common to want to allow different scripts to\ndelegate.\n\n\nOverall, we are left with concerns both about the merit of doing Taproot\nversus alternatives, as well as the process through which we got to be here.\n\n1) Is Taproot actually more private than bare MAST and Schnorr separately?\nWhat\nare the actual anonymity set benefits compared to doing the separately?\n2) Is Taproot actually cheaper than bare MAST and Schnorr separately? What\nevidence do we have that the assumption it will be more common to use\nTaproot\nwith a key will outweigh Script cases?\n3) Is Taproot riskier than bare MAST and Schnorr separately given the new\ncrypto? How well reviewed is the actual crypto parts? None of us personally\nfeel\ncomfortable reviewing the crypto in Schnorr -- what's the set of people who\nhave\nthoroughly reviewed the crypto and aren't just ACKing because they trust\nother\ndevelopers to have looked at it close enough?\n4) Design wise, couldn't we forego the NUMS point requirement and be able to\ncheck if it's a hash root directly? This would encumber users who don't\nneed the\nkey path a cheaper spend path. See thread subject, \"Taproot Public NUMS\nOptimization\".\n5) Is the development model of trying to jam a bunch of features into\nBitcoin\nall at once good for Bitcoin development? Would we be better off if we\nembraced\nincremental improvements that can work together (e.g., MAST and then\nSchnorr)?\nAlthough the BIP raises some points about anonymity sets being why to do\nthem\nall at once, it's not clear to me this argument holds water (same goes for\nbusinesses not upgrading). If we can take things as smaller steps, we are\nnot\nonly more secure, but we also have more time to dedicate review to each\nchange\nindependently. We also end up co-mingling changes that people end up\naccepting\nonly because they want one and they're bundled (e.g., MAST and Schnorr, MAST\nseems like a much less risky addition versus Schnorr). See thread subject,\n\"An\nAlternative Deployment Path for Taproot Technologies\".\n\n\n\n\nOur provocation with this email is primarily that we think we should more\ncarefully consider the benefits of Taproot over simpler primitives that are\nnot\nonly easier to review, but could have been made available much sooner rather\nthan waiting on putting everything all together for an unclear aggregate\nbenefit.\n\nWe do think that most of the developers have been honest about the benefits\nof\nTaproot, but that on closer look we feel the general ecosystem has oversold\nTaproot as being the key enabler for a collection of techniques that we\ncould do\nwith much simpler building blocks.\n\n\nAt the end of the day, we do not strongly advocate not deploying Taproot at\nthis\npoint in the review cycle. We think the Taproot Public NUMS Optimization\nmay be\na good idea, worth considering if it's not insecure, as it cuts through the\ncase\nwhere you would otherwise need a NUMS point. Things like TapScript and its\nMAST\nmechanisms are well designed and offer exciting new deployment paths, and\nwould\nbe something we would use even if we opted for MAST instead of Taproot.\nHowever,\nwe also believe it is our duty to raise these concerns and suggestions, and\nwe\nlook forward to listening to the responses of the community.\n\nGreat thanks,\n\nThe Group\n\nSUBJECT: An Alternative Deployment Path for Taproot Technologies\n\nThis email is the second of a collection of sentiments from a group of\ndevelopers\nwho in aggregate prefer to remain anonymous. These emails have been sent\nunder a\npseudonym so as to keep the focus of discussion on the merits of the\ntechnical\nissues, rather than miring the discussion in personal politics. Our goal\nisn't\nto cause a schism, but rather to help figure out what the path forward is\nwith\nTaproot. To that end, we:\n\n1) Discuss the merits of Taproot's design versus simpler alternatives (see\nthread subject, \"Taproot (and Graftroot) Complexity\").\n2) Propose an alternative path to deploying the technologies described in\nBIP-340, BIP-341, and BIP-342 (see thread subject, \"An Alternative\nDeployment\nPath for Taproot Technologies\").\n3) Suggest a modification to Taproot to reduce some of the overhead (see\nthread\nsubject, \"Taproot Public NUMS Optimization\").\n\nAs a follow up to our prior message, we propose a different path forward\nfor the\nTaproot family of changes:\n\n1) A separate soft-fork for Merkle Branch Witnesses based on Taproot;\n2) A separate soft-fork for Schnorr Signatures\n3) A separate follow up soft-fork which enables Taproot and Graftroot\n\nWe think that the first 2 forks can be offered at the same time or one at a\ntime.\n\nTaproot, as a follow up to changes 1 and 2, can be enabled as a soft-fork\non the\nexisting semantics, but requiring a new witness version. With the Public\nNUMS Optimization, wallets could upgrade by just changing one version byte\nto be\nin the same anonymity set as Taproot.\n\nIt's not clear to us that the time to prepare a BIP and implementation for\n1 and\n2 at this point would be any less than the time to do Taproot as currently\nproposed. However, we believe that such a deployment plan is a reasonable\noption\nas it is more conservative, as Merkle Branch witnesses are relatively\nsimple and\nusers only have to use Schnorr signing if they want to, and can otherwise\ncontinue to use ECDSA. A further benefit of waiting on 3 is that we get to\ncollect real world protocol engineering experience to see how frequently the\nTaproot frequency of use assumption holds, and if it is worth doing or not.\n\n\nGreat thanks,\n\nThe Group\n\n-- \n- Bryan\n://heybryan.org/\n1 512 203 0507\n-------------- next part --------------\nAn attachment was scrubbed...\nURL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20200209/94a71b6f/attachment-0001.html>\nPrevious message: [bitcoin-dev] Purge attacks (spin on sabotage attacks)\nNext message: [bitcoin-dev] An alternative deployment path for taproot technology (Re: Taproot (and graftroot) complexity)\nMessages sorted by: [ date ] [ thread ] [ subject ] [ author ]\nMore information about the bitcoin-dev mailing list\n\n\n://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-February/017615.html",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://github.com/bitcoin/bips/blob/master/bip-0114.mediawiki\",\"http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20200209/94a71b6f/attachment-0001.html\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
steemdelegated 16.290 SP to @alwaysnew
2019/12/26 06:01:24
delegatorsteem
delegateealwaysnew
vesting shares26526.508477 VESTS
Transaction InfoBlock #39367048/Trx 42a0f562807ae6a7259f93f1d27b5cdf06a12cc0
View Raw JSON Data
{
  "trx_id": "42a0f562807ae6a7259f93f1d27b5cdf06a12cc0",
  "block": 39367048,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-12-26T06:01:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "26526.508477 VESTS"
    }
  ]
}
2019/12/22 17:18:06
parent authoralwaysnew
parent permlinkinyfsmj1w6d
authorsteemitboard
permlinksteemitboard-notify-alwaysnew-20191222t171805000z
title
bodyCongratulations @alwaysnew! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@alwaysnew/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@alwaysnew) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=alwaysnew)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #39265570/Trx d6b38b859a4548ccb280759830eded65eb20b484
View Raw JSON Data
{
  "trx_id": "d6b38b859a4548ccb280759830eded65eb20b484",
  "block": 39265570,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-12-22T17:18:06",
  "op": [
    "comment",
    {
      "parent_author": "alwaysnew",
      "parent_permlink": "inyfsmj1w6d",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-alwaysnew-20191222t171805000z",
      "title": "",
      "body": "Congratulations @alwaysnew! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@alwaysnew/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@alwaysnew) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=alwaysnew)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
2019/12/01 18:45:00
voterhozn4ukhlytriwc
authoralwaysnew
permlinkinyfsmj1w6d
weight1500 (15.00%)
Transaction InfoBlock #38663611/Trx 188fed06140995fe570253407ee7d81070f19010
View Raw JSON Data
{
  "trx_id": "188fed06140995fe570253407ee7d81070f19010",
  "block": 38663611,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-12-01T18:45:00",
  "op": [
    "vote",
    {
      "voter": "hozn4ukhlytriwc",
      "author": "alwaysnew",
      "permlink": "inyfsmj1w6d",
      "weight": 1500
    }
  ]
}
yffupvoted (10.00%) @alwaysnew / inyfsmj1w6d
2019/12/01 18:16:06
voteryff
authoralwaysnew
permlinkinyfsmj1w6d
weight1000 (10.00%)
Transaction InfoBlock #38663034/Trx c008b21748ae29b8f473bf1c4ec0ccd4d8e5a2b5
View Raw JSON Data
{
  "trx_id": "c008b21748ae29b8f473bf1c4ec0ccd4d8e5a2b5",
  "block": 38663034,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-12-01T18:16:06",
  "op": [
    "vote",
    {
      "voter": "yff",
      "author": "alwaysnew",
      "permlink": "inyfsmj1w6d",
      "weight": 1000
    }
  ]
}
alwaysnewupdated options for inyfsmj1w6d
2019/12/01 18:14:24
authoralwaysnew
permlinkinyfsmj1w6d
max accepted payout1000000.000 SBD
percent steem dollars10000
allow votestrue
allow curation rewardstrue
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
Transaction InfoBlock #38663000/Trx 2769f65ca1d8de97adc300a590e055cb92754b6f
View Raw JSON Data
{
  "trx_id": "2769f65ca1d8de97adc300a590e055cb92754b6f",
  "block": 38663000,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-12-01T18:14:24",
  "op": [
    "comment_options",
    {
      "author": "alwaysnew",
      "permlink": "inyfsmj1w6d",
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "allow_votes": true,
      "allow_curation_rewards": true,
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ]
    }
  ]
}
alwaysnewpublished a new post: inyfsmj1w6d
2019/12/01 18:14:24
parent author
parent permlinkdtube
authoralwaysnew
permlinkinyfsmj1w6d
titleLove You Like A Bitcoin
body<center><a href='https://d.tube/#!/v/alwaysnew/inyfsmj1w6d'><img src='https://snap1.d.tube/ipfs/QmYEkBMuMbU6zEPYzZUiCgdCE3ZYDvdPvySbBymq4Dh76e'></a></center><hr> happy watching <hr><a href='https://d.tube/#!/v/alwaysnew/inyfsmj1w6d'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmPv8TPS6Lm4mbAE838agmLk7yuizFWyxY9dYZ9RmLug1B'> ▶️ IPFS</a>
json metadata{"video":{"videoId":"QmPv8TPS6Lm4mbAE838agmLk7yuizFWyxY9dYZ9RmLug1B","duration":241.812608,"title":"Love You Like A Bitcoin","description":"happy watching ","filesize":17319194,"ipfs":{"snaphash":"QmQgGTB2FGixpKMXYsuponA9Q5e9QMbzz2P8i6v9DzQZAD","spritehash":"QmXa2CMFZD1UpDi5oRrRboTcrXcTVAbZFH7qjk3639pcpz","videohash":"QmPv8TPS6Lm4mbAE838agmLk7yuizFWyxY9dYZ9RmLug1B","video240hash":"QmZhGHEjdXdkmoburdPmdoD4ndpJyaKoZJuRkSPsp9hUfx"},"thumbnailUrl":"https://snap1.d.tube/ipfs/QmQgGTB2FGixpKMXYsuponA9Q5e9QMbzz2P8i6v9DzQZAD","providerName":"IPFS","refs":[]},"tags":["dtube","gaming"],"app":"dtube/0.9"}
Transaction InfoBlock #38663000/Trx 2769f65ca1d8de97adc300a590e055cb92754b6f
View Raw JSON Data
{
  "trx_id": "2769f65ca1d8de97adc300a590e055cb92754b6f",
  "block": 38663000,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-12-01T18:14:24",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "dtube",
      "author": "alwaysnew",
      "permlink": "inyfsmj1w6d",
      "title": "Love You Like A Bitcoin",
      "body": "<center><a href='https://d.tube/#!/v/alwaysnew/inyfsmj1w6d'><img src='https://snap1.d.tube/ipfs/QmYEkBMuMbU6zEPYzZUiCgdCE3ZYDvdPvySbBymq4Dh76e'></a></center><hr>\n\nhappy watching \n\n<hr><a href='https://d.tube/#!/v/alwaysnew/inyfsmj1w6d'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmPv8TPS6Lm4mbAE838agmLk7yuizFWyxY9dYZ9RmLug1B'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"videoId\":\"QmPv8TPS6Lm4mbAE838agmLk7yuizFWyxY9dYZ9RmLug1B\",\"duration\":241.812608,\"title\":\"Love You Like A Bitcoin\",\"description\":\"happy watching \",\"filesize\":17319194,\"ipfs\":{\"snaphash\":\"QmQgGTB2FGixpKMXYsuponA9Q5e9QMbzz2P8i6v9DzQZAD\",\"spritehash\":\"QmXa2CMFZD1UpDi5oRrRboTcrXcTVAbZFH7qjk3639pcpz\",\"videohash\":\"QmPv8TPS6Lm4mbAE838agmLk7yuizFWyxY9dYZ9RmLug1B\",\"video240hash\":\"QmZhGHEjdXdkmoburdPmdoD4ndpJyaKoZJuRkSPsp9hUfx\"},\"thumbnailUrl\":\"https://snap1.d.tube/ipfs/QmQgGTB2FGixpKMXYsuponA9Q5e9QMbzz2P8i6v9DzQZAD\",\"providerName\":\"IPFS\",\"refs\":[]},\"tags\":[\"dtube\",\"gaming\"],\"app\":\"dtube/0.9\"}"
    }
  ]
}
alwaysnewupdated their account properties
2019/11/20 21:20:36
accountalwaysnew
posting{"weight_threshold":1,"account_auths":[["dlike.app",1],["smartsteem",1],["steemhunt.com",1]],"key_auths":[["STM6KJznVSC1SehjDSw62ATr5SSE63fLZgiA2cShL1YEnDHNukYjE",1]]}
memo keySTM8fc7RBGoh9P6FcdrTG12PJoxKrtyjQAEbsuJ8iC13bRBk9A7ny
json metadata{"profile":{"profile_image":"http://www4.0zz0.com/2017/12/22/22/566536215.jpg","cover_image":"http://www4.0zz0.com/2017/12/22/22/566536215.jpg","dtube_pub":"wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo"}}
Transaction InfoBlock #38350497/Trx 9c29d1ca53aeb4adba1611f5d9e2b70270d734b3
View Raw JSON Data
{
  "trx_id": "9c29d1ca53aeb4adba1611f5d9e2b70270d734b3",
  "block": 38350497,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-20T21:20:36",
  "op": [
    "account_update",
    {
      "account": "alwaysnew",
      "posting": {
        "weight_threshold": 1,
        "account_auths": [
          [
            "dlike.app",
            1
          ],
          [
            "smartsteem",
            1
          ],
          [
            "steemhunt.com",
            1
          ]
        ],
        "key_auths": [
          [
            "STM6KJznVSC1SehjDSw62ATr5SSE63fLZgiA2cShL1YEnDHNukYjE",
            1
          ]
        ]
      },
      "memo_key": "STM8fc7RBGoh9P6FcdrTG12PJoxKrtyjQAEbsuJ8iC13bRBk9A7ny",
      "json_metadata": "{\"profile\":{\"profile_image\":\"http://www4.0zz0.com/2017/12/22/22/566536215.jpg\",\"cover_image\":\"http://www4.0zz0.com/2017/12/22/22/566536215.jpg\",\"dtube_pub\":\"wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo\"}}"
    }
  ]
}
2019/11/17 09:30:30
voterstoodkev
authoralwaysnew
permlinksteem-browser-extension
weight-10000 (-100.00%)
Transaction InfoBlock #38250066/Trx 1d749bc0dc5072fab1bac45b63059b92d3c9c23d
View Raw JSON Data
{
  "trx_id": "1d749bc0dc5072fab1bac45b63059b92d3c9c23d",
  "block": 38250066,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-17T09:30:30",
  "op": [
    "vote",
    {
      "voter": "stoodkev",
      "author": "alwaysnew",
      "permlink": "steem-browser-extension",
      "weight": -10000
    }
  ]
}
steembeemsent 0.001 STEEM to @alwaysnew- "✨ Awesome Auto-Boost Service, with only 1 STEEM per month get all your posts automatically Fully Upvoted! Just send a 1 STEEM with memo 'subscribe', don't be late! find out more on http://www.steembee..."
2019/11/16 21:56:18
fromsteembeem
toalwaysnew
amount0.001 STEEM
memo✨ Awesome Auto-Boost Service, with only 1 STEEM per month get all your posts automatically Fully Upvoted! Just send a 1 STEEM with memo 'subscribe', don't be late! find out more on http://www.steembeem.com
Transaction InfoBlock #38236212/Trx b7e2846344f60366d92d038151edc2c82459cc00
View Raw JSON Data
{
  "trx_id": "b7e2846344f60366d92d038151edc2c82459cc00",
  "block": 38236212,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-16T21:56:18",
  "op": [
    "transfer",
    {
      "from": "steembeem",
      "to": "alwaysnew",
      "amount": "0.001 STEEM",
      "memo": "✨ Awesome Auto-Boost Service, with only 1 STEEM per month get all your posts automatically Fully Upvoted! Just send a 1 STEEM with memo 'subscribe', don't be late! find out more on http://www.steembeem.com"
    }
  ]
}
2019/11/16 21:56:12
voterlaissez-faire
authoralwaysnew
permlinkbitcoin-work-how
weight10000 (100.00%)
Transaction InfoBlock #38236210/Trx 294bbc0050cab1c5169da8d57752e8bee0723a0d
View Raw JSON Data
{
  "trx_id": "294bbc0050cab1c5169da8d57752e8bee0723a0d",
  "block": 38236210,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-16T21:56:12",
  "op": [
    "vote",
    {
      "voter": "laissez-faire",
      "author": "alwaysnew",
      "permlink": "bitcoin-work-how",
      "weight": 10000
    }
  ]
}
2019/11/16 21:56:06
voteranomaly
authoralwaysnew
permlinkbitcoin-work-how
weight100 (1.00%)
Transaction InfoBlock #38236208/Trx 510bf2a27b53219512c5429f6d300729e986a01f
View Raw JSON Data
{
  "trx_id": "510bf2a27b53219512c5429f6d300729e986a01f",
  "block": 38236208,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-16T21:56:06",
  "op": [
    "vote",
    {
      "voter": "anomaly",
      "author": "alwaysnew",
      "permlink": "bitcoin-work-how",
      "weight": 100
    }
  ]
}
alwaysnewpublished a new post: bitcoin-work-how
2019/11/16 21:55:09
parent author
parent permlinksteem
authoralwaysnew
permlinkbitcoin-work-how
titlebitcoin work how !!
bodyConstructing a Taproot output and spending it in the "everyone agrees" case. Shamelessly simplified. ![EJgkKcRVUAIhX0p.jpg](https://cdn.steemitimages.com/DQmbddkqd1uH2uDepN87HGoZrDt26A6C9KdzyF1GGGj9Yak/EJgkKcRVUAIhX0p.jpg)
json metadata{"tags":["steem","bitcoin","crypto"],"image":["https://cdn.steemitimages.com/DQmbddkqd1uH2uDepN87HGoZrDt26A6C9KdzyF1GGGj9Yak/EJgkKcRVUAIhX0p.jpg"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #38236189/Trx a542316589647803cd03026fcca5551cd2b8f435
View Raw JSON Data
{
  "trx_id": "a542316589647803cd03026fcca5551cd2b8f435",
  "block": 38236189,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-16T21:55:09",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "steem",
      "author": "alwaysnew",
      "permlink": "bitcoin-work-how",
      "title": "bitcoin work how !!",
      "body": "Constructing a Taproot output and spending it in the \"everyone agrees\" case. Shamelessly simplified.\n\n\n![EJgkKcRVUAIhX0p.jpg](https://cdn.steemitimages.com/DQmbddkqd1uH2uDepN87HGoZrDt26A6C9KdzyF1GGGj9Yak/EJgkKcRVUAIhX0p.jpg)",
      "json_metadata": "{\"tags\":[\"steem\",\"bitcoin\",\"crypto\"],\"image\":[\"https://cdn.steemitimages.com/DQmbddkqd1uH2uDepN87HGoZrDt26A6C9KdzyF1GGGj9Yak/EJgkKcRVUAIhX0p.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2019/11/15 16:32:21
voterfilipino
authoralwaysnew
permlinksteem-browser-extension
weight1000 (10.00%)
Transaction InfoBlock #38201019/Trx 6bbf5845b000124d4862f66b2e7dada18011a726
View Raw JSON Data
{
  "trx_id": "6bbf5845b000124d4862f66b2e7dada18011a726",
  "block": 38201019,
  "trx_in_block": 27,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-15T16:32:21",
  "op": [
    "vote",
    {
      "voter": "filipino",
      "author": "alwaysnew",
      "permlink": "steem-browser-extension",
      "weight": 1000
    }
  ]
}
2019/11/15 15:52:06
parent authoralwaysnew
parent permlinksteem-browser-extension
authorcheetah
permlinkcheetah-re-alwaysnewsteem-browser-extension
title
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://busy.org/@yabapmatt/sps-proposal-for-steem-keychain-development
json metadata
Transaction InfoBlock #38200216/Trx fa8325d8aed29445e78ef3a2e9a425b669352e03
View Raw JSON Data
{
  "trx_id": "fa8325d8aed29445e78ef3a2e9a425b669352e03",
  "block": 38200216,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-15T15:52:06",
  "op": [
    "comment",
    {
      "parent_author": "alwaysnew",
      "parent_permlink": "steem-browser-extension",
      "author": "cheetah",
      "permlink": "cheetah-re-alwaysnewsteem-browser-extension",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://busy.org/@yabapmatt/sps-proposal-for-steem-keychain-development",
      "json_metadata": ""
    }
  ]
}
2019/11/15 15:52:03
votercheetah
authoralwaysnew
permlinksteem-browser-extension
weight8 (0.08%)
Transaction InfoBlock #38200215/Trx 63931d0f927e690992abc48bce81840d52868c14
View Raw JSON Data
{
  "trx_id": "63931d0f927e690992abc48bce81840d52868c14",
  "block": 38200215,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-15T15:52:03",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "alwaysnew",
      "permlink": "steem-browser-extension",
      "weight": 8
    }
  ]
}
alwaysnewpublished a new post: steem-browser-extension
2019/11/15 15:51:45
parent author
parent permlinksteem
authoralwaysnew
permlinksteem-browser-extension
titlesteem browser extension
bodySteem Keychain is a browser extension currently available for the Chrome, Brave, and Firefox web browsers that allows users to securely store their Steem keys for multiple accounts and seamlessly interact with nearly all available Steem apps. It also provides a number of convenient features right within the extension such as: ![yyyy.png](https://cdn.steemitimages.com/DQmdDHUftkHRrq27zMrF6Fs8sYKfAEsiPtERbD4vompDxh9/yyyy.png) Checking balances, resource credits, and voting power; Transferring STEEM / SBD and viewing transaction history; Managing power ups, power downs, and SP delegations; Managing witness votes; and Viewing and transferring Steem Engine tokens. It is available to download and install from the following locations: Chrome / Brave: https://chrome.google.com/webstore/detail/steem-keychain/lkcjlnjfpbikmcmbachjpdbijejflpcm?hl=en Firefox: https://addons.mozilla.org/en-US/firefox/addon/steem-keychain/ Source Code: https://github.com/MattyIce/steem-keychain Request for Funding @aggroed and I have been personally funding the initial creation and ongoing development of the Steem Keychain extension over the past year or so and we are extremely fortunate to have been in a position to do that - all thanks to the Steem platform and community. Going forward, we would like to utilize the new Steem Proposal System to ask the Steem community to help support the costs of continued development and maintenance of this project in the future. We are requesting 100 SBD per day for the next 6 months. This comes to 3000 SBD per month, which is approximately $2000 USD per month at current market prices for SBD. The funds will be used to pay for development and/or design work to add new features to the extension, keep it updated with any changes released to Steem or Steem Engine, and fix bugs and issues that are reported. The amount of funds requested is an estimate of what may be needed based on past history, and any unused funds will be returned to the @steem.dao account to be put back into other projects. At the end of each month we will publish a report detailing what work was done and what funds were used for the community to review. The list of tasks currently in progress or planned for the near future are as follows: Add the ability for apps to choose which RPC node the extension should use to broadcast transactions (from a pre-approved list of available nodes only for security reasons) Allow a default RPC node to be set and updated remotely by the development team Code cleanup and refactor Add ability for sites/apps that create accounts to automatically add the new account to the keychain extension if it is available Advanced design and planning for SMT / communities integration Improved documentation & error messaging Localization support Why This is Important for Steem Steem is a platform primarily focused on powering web applications, and as such it's very important that it be as simple and secure as possible for users to interact with those applications if we want to have any hope of serious growth. While there are a number of different ways to store keys and sign/broadcast transactions, a browser extension provides the best overall user experience without trading off security, which is essential. Steem, unfortunately, doesn't have the best reputation within the cryptocurrency community, so if we want to have any chance of changing that perception we need to not only have all of the tools users are expecting, but they must be easy to use, well designed, and be actively updated and maintained. Professional, user-friendly, well maintained products give people confidence in a project while buggy, complicated, and poorly-designed products drive people away. If Steem can inspire confidence in the community through the quality of its products and apps then that confidence should eventually be reflected in the markets. Of course, professional, user-friendly, well maintained products require funding to create. It's usually pretty easy to tell which products were created by a couple people in their spare time vs the ones that have a properly funded team. Many of the projects on Steem in the past have fallen in the former category, but our hope is that via the new Steem Proposal System that will start to change. That's why the SPS is such an important addition to the Steem ecosystem, but it won't achieve that goal by itself. It will require good teams to submit and deliver on great proposals, and it will require the Steem stakeholders to make smart decisions in the allocation of the available funds and to ensure that the teams behind funded projects actually deliver at the level of quality that we need. We Need Your Vote! The Steem Keychain extension currently has over 5000 users and growing (according to data from the Chrome and Mozilla web stores), and I like to think that the team behind it (including myself, @aggroed, @stoodkev, and @nateaguila) has a decent track record of delivering results. So if you feel that this is a worthwhile project and would like it to receive funding through the SPS, please consider giving it your vote! You can view and vote for proposals at the following sites: Vote for this Proposal using SteemConnect Steem Proposals: https://steemproposals.com/proposal/55 SteemPeak: https://steempeak.com/me/proposals Steemit Wallet: https://steemitwallet.com/proposals
json metadata{"tags":["steem","bitcoin","crypto"],"users":["aggroed","steem.dao","stoodkev","nateaguila"],"image":["https://cdn.steemitimages.com/DQmdDHUftkHRrq27zMrF6Fs8sYKfAEsiPtERbD4vompDxh9/yyyy.png"],"links":["https://chrome.google.com/webstore/detail/steem-keychain/lkcjlnjfpbikmcmbachjpdbijejflpcm?hl=en","https://addons.mozilla.org/en-US/firefox/addon/steem-keychain/","https://github.com/MattyIce/steem-keychain","https://steemproposals.com/proposal/55","https://steempeak.com/me/proposals","https://steemitwallet.com/proposals"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #38200209/Trx 34be15186c55910e6d45bdae83d7dbfa5540123e
View Raw JSON Data
{
  "trx_id": "34be15186c55910e6d45bdae83d7dbfa5540123e",
  "block": 38200209,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-15T15:51:45",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "steem",
      "author": "alwaysnew",
      "permlink": "steem-browser-extension",
      "title": "steem browser extension",
      "body": "Steem Keychain is a browser extension currently available for the Chrome, Brave, and Firefox web browsers that allows users to securely store their Steem keys for multiple accounts and seamlessly interact with nearly all available Steem apps. It also provides a number of convenient features right within the extension such as:\n\n\n![yyyy.png](https://cdn.steemitimages.com/DQmdDHUftkHRrq27zMrF6Fs8sYKfAEsiPtERbD4vompDxh9/yyyy.png)\n\n\n\nChecking balances, resource credits, and voting power;\nTransferring STEEM / SBD and viewing transaction history;\nManaging power ups, power downs, and SP delegations;\nManaging witness votes; and\nViewing and transferring Steem Engine tokens.\nIt is available to download and install from the following locations:\n\nChrome / Brave: https://chrome.google.com/webstore/detail/steem-keychain/lkcjlnjfpbikmcmbachjpdbijejflpcm?hl=en\nFirefox: https://addons.mozilla.org/en-US/firefox/addon/steem-keychain/\nSource Code: https://github.com/MattyIce/steem-keychain\nRequest for Funding\n@aggroed and I have been personally funding the initial creation and ongoing development of the Steem Keychain extension over the past year or so and we are extremely fortunate to have been in a position to do that - all thanks to the Steem platform and community.\n\nGoing forward, we would like to utilize the new Steem Proposal System to ask the Steem community to help support the costs of continued development and maintenance of this project in the future.\n\nWe are requesting 100 SBD per day for the next 6 months. This comes to 3000 SBD per month, which is approximately $2000 USD per month at current market prices for SBD.\n\nThe funds will be used to pay for development and/or design work to add new features to the extension, keep it updated with any changes released to Steem or Steem Engine, and fix bugs and issues that are reported. The amount of funds requested is an estimate of what may be needed based on past history, and any unused funds will be returned to the @steem.dao account to be put back into other projects.\n\nAt the end of each month we will publish a report detailing what work was done and what funds were used for the community to review. The list of tasks currently in progress or planned for the near future are as follows:\n\nAdd the ability for apps to choose which RPC node the extension should use to broadcast transactions (from a pre-approved list of available nodes only for security reasons)\nAllow a default RPC node to be set and updated remotely by the development team\nCode cleanup and refactor\nAdd ability for sites/apps that create accounts to automatically add the new account to the keychain extension if it is available\nAdvanced design and planning for SMT / communities integration\nImproved documentation & error messaging\nLocalization support\nWhy This is Important for Steem\nSteem is a platform primarily focused on powering web applications, and as such it's very important that it be as simple and secure as possible for users to interact with those applications if we want to have any hope of serious growth. While there are a number of different ways to store keys and sign/broadcast transactions, a browser extension provides the best overall user experience without trading off security, which is essential.\n\nSteem, unfortunately, doesn't have the best reputation within the cryptocurrency community, so if we want to have any chance of changing that perception we need to not only have all of the tools users are expecting, but they must be easy to use, well designed, and be actively updated and maintained.\n\nProfessional, user-friendly, well maintained products give people confidence in a project while buggy, complicated, and poorly-designed products drive people away. If Steem can inspire confidence in the community through the quality of its products and apps then that confidence should eventually be reflected in the markets.\n\nOf course, professional, user-friendly, well maintained products require funding to create. It's usually pretty easy to tell which products were created by a couple people in their spare time vs the ones that have a properly funded team. Many of the projects on Steem in the past have fallen in the former category, but our hope is that via the new Steem Proposal System that will start to change.\n\nThat's why the SPS is such an important addition to the Steem ecosystem, but it won't achieve that goal by itself. It will require good teams to submit and deliver on great proposals, and it will require the Steem stakeholders to make smart decisions in the allocation of the available funds and to ensure that the teams behind funded projects actually deliver at the level of quality that we need.\n\nWe Need Your Vote!\nThe Steem Keychain extension currently has over 5000 users and growing (according to data from the Chrome and Mozilla web stores), and I like to think that the team behind it (including myself, @aggroed, @stoodkev, and @nateaguila) has a decent track record of delivering results. So if you feel that this is a worthwhile project and would like it to receive funding through the SPS, please consider giving it your vote!\n\nYou can view and vote for proposals at the following sites:\n\nVote for this Proposal using SteemConnect\nSteem Proposals: https://steemproposals.com/proposal/55\nSteemPeak: https://steempeak.com/me/proposals\nSteemit Wallet: https://steemitwallet.com/proposals",
      "json_metadata": "{\"tags\":[\"steem\",\"bitcoin\",\"crypto\"],\"users\":[\"aggroed\",\"steem.dao\",\"stoodkev\",\"nateaguila\"],\"image\":[\"https://cdn.steemitimages.com/DQmdDHUftkHRrq27zMrF6Fs8sYKfAEsiPtERbD4vompDxh9/yyyy.png\"],\"links\":[\"https://chrome.google.com/webstore/detail/steem-keychain/lkcjlnjfpbikmcmbachjpdbijejflpcm?hl=en\",\"https://addons.mozilla.org/en-US/firefox/addon/steem-keychain/\",\"https://github.com/MattyIce/steem-keychain\",\"https://steemproposals.com/proposal/55\",\"https://steempeak.com/me/proposals\",\"https://steemitwallet.com/proposals\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2019/10/29 12:10:06
parent authoralwaysnew
parent permlinkdcep-china-s-national-digital-currency-overview
authorcheetah
permlinkcheetah-re-alwaysnewdcep-china-s-national-digital-currency-overview
title
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://boxmining.com/dcep/
json metadata
Transaction InfoBlock #37707141/Trx 2bb51a9d9deda8026f79698fb34412e0ccfff30b
View Raw JSON Data
{
  "trx_id": "2bb51a9d9deda8026f79698fb34412e0ccfff30b",
  "block": 37707141,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-29T12:10:06",
  "op": [
    "comment",
    {
      "parent_author": "alwaysnew",
      "parent_permlink": "dcep-china-s-national-digital-currency-overview",
      "author": "cheetah",
      "permlink": "cheetah-re-alwaysnewdcep-china-s-national-digital-currency-overview",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://boxmining.com/dcep/",
      "json_metadata": ""
    }
  ]
}
2019/10/29 12:10:00
votercheetah
authoralwaysnew
permlinkdcep-china-s-national-digital-currency-overview
weight8 (0.08%)
Transaction InfoBlock #37707139/Trx 4bbb5890ddcccdebbf2f6a7f54531822b5082252
View Raw JSON Data
{
  "trx_id": "4bbb5890ddcccdebbf2f6a7f54531822b5082252",
  "block": 37707139,
  "trx_in_block": 30,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-29T12:10:00",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "alwaysnew",
      "permlink": "dcep-china-s-national-digital-currency-overview",
      "weight": 8
    }
  ]
}
2019/10/29 12:09:36
parent author
parent permlinksteem
authoralwaysnew
permlinkdcep-china-s-national-digital-currency-overview
titleDCEP: China’s National Digital Currency Overview
bodyDigital Currency DCEP (Digitial Currency Electronic Payment, DC/EP) is a national digital currency of the China built with Blockchain and Cryptographic technology. The currency is pegged 1:1 to the Chinese National Currency – the RenMinBi (RMB). The overall objective of the currency is to increase the circulation of the RMB and international reach – with eventual hopes that the RMB will the a global currency like the US Dollar. DCEP is the only legal digital currency in China (cryptocurrency such as Bitcoin are not legal tender in China). Huang Qifan (Chairman of the China International Economic Exchange Center) said they have been working on DCEP for five to six years now and is fully confident it can be introduced as the country’s financial system. It’s currently being rolled out, with the People’s Bank of China (PBoC) issuing the currency. DCEP CAN ACHIEVE REAL-TIME COLLECTION OF DATA RELATED TO MONEY CREATION, BOOKKEEPING, ETC, PROVIDING USEFUL REFERENCE FOR THE PROVISION OF MONEY AND THE IMPLEMENTATION OF MONETARY POLICIES ![DCEP-security-1024x573.jpg](https://cdn.steemitimages.com/DQmNxbDTe1WpAyC2TbjfyQs2Q1rqSC6EqfrtUzCzefZ8Vn9/DCEP-security-1024x573.jpg) Deployment and Distribution DCEP will initially be distributed to all commercial banks affiliated with the Chinese Central Bank such as ICBC and Agriculture Bank of China. The significance of DCEP is that it’s designed as a replacement of the Reserve Money (M0) system, cutting back the cost and friction of bank transfers. This initial deployment will serve as an official production test for the currency system, where the network and security will be validated. In the second phase, DCEP will be distributed to large fintech companies such as Tencent and Alibaba to be used in WeChat Pay and AliPay respectively. Mandate to adopt Blockchain President Xi JinPing has mandated that the ‘country’s development of blockchain technology should be sped up ‘ on Oct 24th in front of the Political Bureau. This speech has also been echoed by Li Wei, head of the People’s Bank of China. China has adopted the “Blockchain, not Cryptocurrency”, whereby the benefits of Blockchain is highlighted. On the other hand, cryptocurrencies that are native to Blockchain are suppressed as Cryptocurrency Exchanges and ICOs are banned in the country. ![maxresdefault.jpg](https://cdn.steemitimages.com/DQmYVLKrYnS9Ef7cJsbfHbi79VscBHaPsBP1CYZSXcXah9N/maxresdefault.jpg) DCEP is a Centralized Currency DCEP is a digital currency that is run on a centralized private network – the Central Bank of China has complete access and control of the currency. This is a huge contrast to Bitcoin, which has an open decentralized network where there is no centralized leader. In the case with DCEP, the Central bank of China has the ability to create or destroy DCEP. Note: Previous publications have referred to the national currency as CBDC. Sources: https://venturebeat.com/2019/09/15/wake-up-us-federal-reserve-china-just-showed-how-digital-currency-is-done/ https://www.reuters.com/article/us-china-blockchain-idUSKBN1X704A https://u.today/just-in-chinese-central-bank-to-launch-digital-currency-called-dcep https://beincrypto.com/chinas-dcep-to-be-worlds-first-national-digital-currency-says-ccie-vice-chairman/ https://qz.com/1710850/chinas-central-bank-could-gain-from-a-digital-yuan-cbdc/
json metadata{"tags":["steem","bitcoin","crypto"],"image":["https://cdn.steemitimages.com/DQmNxbDTe1WpAyC2TbjfyQs2Q1rqSC6EqfrtUzCzefZ8Vn9/DCEP-security-1024x573.jpg","https://cdn.steemitimages.com/DQmYVLKrYnS9Ef7cJsbfHbi79VscBHaPsBP1CYZSXcXah9N/maxresdefault.jpg"],"links":["https://venturebeat.com/2019/09/15/wake-up-us-federal-reserve-china-just-showed-how-digital-currency-is-done/","https://www.reuters.com/article/us-china-blockchain-idUSKBN1X704A","https://u.today/just-in-chinese-central-bank-to-launch-digital-currency-called-dcep","https://beincrypto.com/chinas-dcep-to-be-worlds-first-national-digital-currency-says-ccie-vice-chairman/","https://qz.com/1710850/chinas-central-bank-could-gain-from-a-digital-yuan-cbdc/"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #37707131/Trx 0bb7543853c3d5d78516cf017562ab934573af28
View Raw JSON Data
{
  "trx_id": "0bb7543853c3d5d78516cf017562ab934573af28",
  "block": 37707131,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-29T12:09:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "steem",
      "author": "alwaysnew",
      "permlink": "dcep-china-s-national-digital-currency-overview",
      "title": "DCEP: China’s National Digital Currency Overview",
      "body": "Digital Currency DCEP (Digitial Currency Electronic Payment, DC/EP) is a national digital currency of the China built with Blockchain and Cryptographic technology. The currency is pegged 1:1 to the Chinese National Currency – the RenMinBi (RMB). The overall objective of the currency is to increase the circulation of the RMB and international reach – with eventual hopes that the RMB will the a global currency like the US Dollar. DCEP is the only legal digital currency in China (cryptocurrency such as Bitcoin are not legal tender in China).\n\nHuang Qifan (Chairman of the China International Economic Exchange Center) said they have been working on DCEP for five to six years now and is fully confident it can be introduced as the country’s financial system. It’s currently being rolled out, with the People’s Bank of China (PBoC) issuing the currency.\n\nDCEP CAN ACHIEVE REAL-TIME COLLECTION OF DATA RELATED TO MONEY CREATION, BOOKKEEPING, ETC, PROVIDING USEFUL REFERENCE FOR THE PROVISION OF MONEY AND THE IMPLEMENTATION OF MONETARY POLICIES\n\n\n![DCEP-security-1024x573.jpg](https://cdn.steemitimages.com/DQmNxbDTe1WpAyC2TbjfyQs2Q1rqSC6EqfrtUzCzefZ8Vn9/DCEP-security-1024x573.jpg)\n\nDeployment and Distribution\nDCEP will initially be distributed to all commercial banks affiliated with the Chinese Central Bank such as ICBC and Agriculture Bank of China. The significance of DCEP is that it’s designed as a replacement of the Reserve Money (M0) system, cutting back the cost and friction of bank transfers. This initial deployment will serve as an official production test for the currency system, where the network and security will be validated. In the second phase, DCEP will be distributed to large fintech companies such as Tencent and Alibaba to be used in WeChat Pay and AliPay respectively.\n\nMandate to adopt Blockchain\nPresident Xi JinPing has mandated that the ‘country’s development of blockchain technology should be sped up ‘ on Oct 24th in front of the Political Bureau. This speech has also been echoed by Li Wei, head of the People’s Bank of China. China has adopted the “Blockchain, not Cryptocurrency”, whereby the benefits of Blockchain is highlighted. On the other hand, cryptocurrencies that are native to Blockchain are suppressed as Cryptocurrency Exchanges and ICOs are banned in the country.\n\n![maxresdefault.jpg](https://cdn.steemitimages.com/DQmYVLKrYnS9Ef7cJsbfHbi79VscBHaPsBP1CYZSXcXah9N/maxresdefault.jpg)\n\n\nDCEP is a Centralized Currency\nDCEP is a digital currency that is run on a centralized private network – the Central Bank of China has complete access and control of the currency. This is a huge contrast to Bitcoin, which has an open decentralized network where there is no centralized leader. In the case with DCEP, the Central bank of China has the ability to create or destroy DCEP.\n\nNote: Previous publications have referred to the national currency as CBDC.\n\nSources:\nhttps://venturebeat.com/2019/09/15/wake-up-us-federal-reserve-china-just-showed-how-digital-currency-is-done/\nhttps://www.reuters.com/article/us-china-blockchain-idUSKBN1X704A\nhttps://u.today/just-in-chinese-central-bank-to-launch-digital-currency-called-dcep\nhttps://beincrypto.com/chinas-dcep-to-be-worlds-first-national-digital-currency-says-ccie-vice-chairman/\nhttps://qz.com/1710850/chinas-central-bank-could-gain-from-a-digital-yuan-cbdc/",
      "json_metadata": "{\"tags\":[\"steem\",\"bitcoin\",\"crypto\"],\"image\":[\"https://cdn.steemitimages.com/DQmNxbDTe1WpAyC2TbjfyQs2Q1rqSC6EqfrtUzCzefZ8Vn9/DCEP-security-1024x573.jpg\",\"https://cdn.steemitimages.com/DQmYVLKrYnS9Ef7cJsbfHbi79VscBHaPsBP1CYZSXcXah9N/maxresdefault.jpg\"],\"links\":[\"https://venturebeat.com/2019/09/15/wake-up-us-federal-reserve-china-just-showed-how-digital-currency-is-done/\",\"https://www.reuters.com/article/us-china-blockchain-idUSKBN1X704A\",\"https://u.today/just-in-chinese-central-bank-to-launch-digital-currency-called-dcep\",\"https://beincrypto.com/chinas-dcep-to-be-worlds-first-national-digital-currency-says-ccie-vice-chairman/\",\"https://qz.com/1710850/chinas-central-bank-could-gain-from-a-digital-yuan-cbdc/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2019/10/04 18:06:57
voterlaissez-faire
authoralwaysnew
permlinkmimblewimble
weight10000 (100.00%)
Transaction InfoBlock #36995717/Trx c61a7181a55250beee03d3e3cb3df89bc36d8b4b
View Raw JSON Data
{
  "trx_id": "c61a7181a55250beee03d3e3cb3df89bc36d8b4b",
  "block": 36995717,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-04T18:06:57",
  "op": [
    "vote",
    {
      "voter": "laissez-faire",
      "author": "alwaysnew",
      "permlink": "mimblewimble",
      "weight": 10000
    }
  ]
}
2019/10/04 18:06:51
voteranomaly
authoralwaysnew
permlinkmimblewimble
weight100 (1.00%)
Transaction InfoBlock #36995715/Trx 164b10b6f82b6b85b3dea0df90c9852d914190d6
View Raw JSON Data
{
  "trx_id": "164b10b6f82b6b85b3dea0df90c9852d914190d6",
  "block": 36995715,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-04T18:06:51",
  "op": [
    "vote",
    {
      "voter": "anomaly",
      "author": "alwaysnew",
      "permlink": "mimblewimble",
      "weight": 100
    }
  ]
}
alwaysnewpublished a new post: mimblewimble
2019/10/04 18:05:48
parent author
parent permlinksteem
authoralwaysnew
permlinkmimblewimble
titleMimblewimble
bodyMimblewimble is a blockchain-based distributed registry design that differs in many ways from that of Bitcoin. It offers interesting differences from the point of view of the confidentiality of transactions and "scripting" at the cost of a sacrifice in terms of functionality or even transaction throughput per second. However, the operating principles of Lightning Network, in a simplified version, could apply to Mimblewimble which reduces the importance of the latter disadvantage in terms of loss of flow. Mimblewimble builds on the ideas of Blockstream Confidential Transaction and adds the ability to combine transactions with each other, remove the "outputs" that are no longer expendable (UTXO) to keep only the unspent "outputs" that reduce that makes the total size of the chain considerably. This ability to reduce the size of the blockchain over time is important, especially in the context of confidential transactions: in fact, the fact of masking the amount of the transactions is accompanied by an increase in information that is related to the transaction and ensure that the amount of the output does not behave like a negative amount which would lead to an attack to create money from scratch. To give an order of magnitude, if the bitcoin blockchain implemented the confidential transaction technology of "Ct Element" the total size of the string would exceed 1 Tera byte. MimbleWimble therefore allows newcomers to the network not to download the history of past (spent) outputs and to suppress the "inputs" to keep only "unspent outputs" and money creation inputs. It is nevertheless impossible to claim that a transaction did not take place even if the input and output were erased because the combined transactions contain a cryptographic trace (sum of "Excess") of all the transactions including those which have been deleted. This technology, in a first approach, seems to make the scripting impossible because they can not be the object of operation of addition or subtraction like the amounts and the keys. In addition, deleting the history of past transactions would not allow nodes to replay the scripts related to the outputs. But that nay! The magic of signatures ("magicking digital signatures" in the words of Andrew Poelstra) means that some of them can be created only through the good faith execution of a computer program. If we combine this capacity with the principles underlying Lightning Network's HTLCs, we then have funds that can only be released after the successful execution of a program, ie the publication of the signature. adequate. The scripts would no longer be executed by the nodes of the blockchain (as happens on Ethereum or Bitcoin) but only on the computers of the actors concerned: only the signature and the public key proving the execution of a program would be visible. This is a considerable advance in terms of the confidentiality of the interactions between the actors of a contract because the "Scriptless Script" are stored and executed outside blockchain. These "scripts", however, have limitations. They will be the subject of a future study by project contributors. To date, Mimblewimble is in the process of specification and development and is not yet usable. The implementation could be done in several ways in the future: an extension on the Bitcoin network via a softfork, a sidechain or in the form of an altcoin.
json metadata{"tags":["steem"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #36995694/Trx 23ffab8f8e43dac1789b34fa7c838f26c7ba0e83
View Raw JSON Data
{
  "trx_id": "23ffab8f8e43dac1789b34fa7c838f26c7ba0e83",
  "block": 36995694,
  "trx_in_block": 30,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-04T18:05:48",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "steem",
      "author": "alwaysnew",
      "permlink": "mimblewimble",
      "title": "Mimblewimble",
      "body": "Mimblewimble is a blockchain-based distributed registry design that differs in many ways from that of Bitcoin. It offers interesting differences from the point of view of the confidentiality of transactions and \"scripting\" at the cost of a sacrifice in terms of functionality or even transaction throughput per second. However, the operating principles of Lightning Network, in a simplified version, could apply to Mimblewimble which reduces the importance of the latter disadvantage in terms of loss of flow.\n\nMimblewimble builds on the ideas of Blockstream Confidential Transaction and adds the ability to combine transactions with each other, remove the \"outputs\" that are no longer expendable (UTXO) to keep only the unspent \"outputs\" that reduce that makes the total size of the chain considerably.\n\nThis ability to reduce the size of the blockchain over time is important, especially in the context of confidential transactions: in fact, the fact of masking the amount of the transactions is accompanied by an increase in information that is related to the transaction and ensure that the amount of the output does not behave like a negative amount which would lead to an attack to create money from scratch. To give an order of magnitude, if the bitcoin blockchain implemented the confidential transaction technology of \"Ct Element\" the total size of the string would exceed 1 Tera byte.\n\nMimbleWimble therefore allows newcomers to the network not to download the history of past (spent) outputs and to suppress the \"inputs\" to keep only \"unspent outputs\" and money creation inputs.\n\nIt is nevertheless impossible to claim that a transaction did not take place even if the input and output were erased because the combined transactions contain a cryptographic trace (sum of \"Excess\") of all the transactions including those which have been deleted.\n\nThis technology, in a first approach, seems to make the scripting impossible because they can not be the object of operation of addition or subtraction like the amounts and the keys. In addition, deleting the history of past transactions would not allow nodes to replay the scripts related to the outputs. But that nay! The magic of signatures (\"magicking digital signatures\" in the words of Andrew Poelstra) means that some of them can be created only through the good faith execution of a computer program. If we combine this capacity with the principles underlying Lightning Network's HTLCs, we then have funds that can only be released after the successful execution of a program, ie the publication of the signature. adequate. The scripts would no longer be executed by the nodes of the blockchain (as happens on Ethereum or Bitcoin) but only on the computers of the actors concerned: only the signature and the public key proving the execution of a program would be visible.\n\nThis is a considerable advance in terms of the confidentiality of the interactions between the actors of a contract because the \"Scriptless Script\" are stored and executed outside blockchain. These \"scripts\", however, have limitations. They will be the subject of a future study by project contributors.\n\nTo date, Mimblewimble is in the process of specification and development and is not yet usable. The implementation could be done in several ways in the future: an extension on the Bitcoin network via a softfork, a sidechain or in the form of an altcoin.",
      "json_metadata": "{\"tags\":[\"steem\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2019/10/02 12:01:36
required auths[]
required posting auths["alwaysnew"]
idfollow
json["follow",{"follower":"alwaysnew","following":"ganza","what":["blog"]}]
Transaction InfoBlock #36930946/Trx a8e0171bb7579dd4d516a87cd095cc7859a37442
View Raw JSON Data
{
  "trx_id": "a8e0171bb7579dd4d516a87cd095cc7859a37442",
  "block": 36930946,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-02T12:01:36",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "alwaysnew"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"alwaysnew\",\"following\":\"ganza\",\"what\":[\"blog\"]}]"
    }
  ]
}
2019/10/02 12:01:30
required auths[]
required posting auths["alwaysnew"]
idfollow
json["follow",{"follower":"alwaysnew","following":"ganza","what":["blog"]}]
Transaction InfoBlock #36930944/Trx a8168f92bf958fec243b01bbcbf6988539a9c9d4
View Raw JSON Data
{
  "trx_id": "a8168f92bf958fec243b01bbcbf6988539a9c9d4",
  "block": 36930944,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-02T12:01:30",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "alwaysnew"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"alwaysnew\",\"following\":\"ganza\",\"what\":[\"blog\"]}]"
    }
  ]
}
alwaysnewreplied to @ganza / pyqxe1
2019/10/02 12:01:24
parent authorganza
parent permlinkfollow-us-on-social-networks
authoralwaysnew
permlinkpyqxe1
title
bodygood project
json metadata{"app":"steemit/0.1"}
Transaction InfoBlock #36930942/Trx 57b958fff20c3253ff0a6140f7061ccb9a354d2a
View Raw JSON Data
{
  "trx_id": "57b958fff20c3253ff0a6140f7061ccb9a354d2a",
  "block": 36930942,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-02T12:01:24",
  "op": [
    "comment",
    {
      "parent_author": "ganza",
      "parent_permlink": "follow-us-on-social-networks",
      "author": "alwaysnew",
      "permlink": "pyqxe1",
      "title": "",
      "body": "good project",
      "json_metadata": "{\"app\":\"steemit/0.1\"}"
    }
  ]
}
2019/10/02 12:01:12
voteralwaysnew
authorganza
permlinkfollow-us-on-social-networks
weight-10000 (-100.00%)
Transaction InfoBlock #36930938/Trx 1c525a4315ef197cc1384858b645ef6ca5baeb7a
View Raw JSON Data
{
  "trx_id": "1c525a4315ef197cc1384858b645ef6ca5baeb7a",
  "block": 36930938,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-02T12:01:12",
  "op": [
    "vote",
    {
      "voter": "alwaysnew",
      "author": "ganza",
      "permlink": "follow-us-on-social-networks",
      "weight": -10000
    }
  ]
}
2019/09/30 19:06:36
voterelowin
authoralwaysnew
permlinkbuilding-your-own-bitcoin-satellite-node
weight8000 (80.00%)
Transaction InfoBlock #36881946/Trx 7a41ec7c09ea612232f99528273d80ab852c6f73
View Raw JSON Data
{
  "trx_id": "7a41ec7c09ea612232f99528273d80ab852c6f73",
  "block": 36881946,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-30T19:06:36",
  "op": [
    "vote",
    {
      "voter": "elowin",
      "author": "alwaysnew",
      "permlink": "building-your-own-bitcoin-satellite-node",
      "weight": 8000
    }
  ]
}
2019/09/30 18:45:21
parent authoralwaysnew
parent permlinkbuilding-your-own-bitcoin-satellite-node
authorcheetah
permlinkcheetah-re-alwaysnewbuilding-your-own-bitcoin-satellite-node
title
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://hackernoon.com/building-your-own-bitcoin-satellite-node-6061d3c93e7
json metadata
Transaction InfoBlock #36881522/Trx 104918dfde0f6ade3db6800d352a39e5ce33b99c
View Raw JSON Data
{
  "trx_id": "104918dfde0f6ade3db6800d352a39e5ce33b99c",
  "block": 36881522,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-30T18:45:21",
  "op": [
    "comment",
    {
      "parent_author": "alwaysnew",
      "parent_permlink": "building-your-own-bitcoin-satellite-node",
      "author": "cheetah",
      "permlink": "cheetah-re-alwaysnewbuilding-your-own-bitcoin-satellite-node",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://hackernoon.com/building-your-own-bitcoin-satellite-node-6061d3c93e7",
      "json_metadata": ""
    }
  ]
}
2019/09/30 18:45:18
votercheetah
authoralwaysnew
permlinkbuilding-your-own-bitcoin-satellite-node
weight8 (0.08%)
Transaction InfoBlock #36881521/Trx 19d23ca0b628752c0ea9db189556a6ca5b9d0b7f
View Raw JSON Data
{
  "trx_id": "19d23ca0b628752c0ea9db189556a6ca5b9d0b7f",
  "block": 36881521,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-30T18:45:18",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "alwaysnew",
      "permlink": "building-your-own-bitcoin-satellite-node",
      "weight": 8
    }
  ]
}
2019/09/30 18:44:57
parent author
parent permlinksteem
authoralwaysnew
permlinkbuilding-your-own-bitcoin-satellite-node
titleBuilding Your Own Bitcoin Satellite Node
body![1_gN909Ok7Ei98Fdl-Zx94NQ.png](https://cdn.steemitimages.com/DQmXt1HjrFHA7bH14UbrdNApwZtpAtf2z2MkSiabk19w9pm/1_gN909Ok7Ei98Fdl-Zx94NQ.png) Hardware requirements: Note: The Amazon affiliate links are just to show what parts to get. You can undoubtedly find the parts on eBay if you want to. I realize some of the parts may be sold out on Amazon at this time. This guide was written for the parts on this list. A computer with Linux installed. This guide uses Fedora 26. I went with Fedora because it is free, it is compatible with the software required, and because it has a large user base. Make sure to have an i5 or a similarly performant processor: https://amzn.to/2x6G86r Note: It is now possible to run the Satellite receiver software on a Raspberry Pi or similar device! If using Ubuntu or another Debian-based distro, you can just add the PPA and apt install satellite ! Ample storage space (roughly 4GB for a pruned node, 150GB+ for non-pruned) At least a 46cm (18") satellite dish: https://amzn.to/2wBtPzK Software Defined Radio Interface: https://amzn.to/2g8Nu2O Linear Polarization PLL LNB: https://amzn.to/2w0Zk4C LNB Mounting Bracket: https://amzn.to/2xgotXU LNB Power Supply: https://amzn.to/2KUGouq Coax Cable: https://amzn.to/2w7N4xQ F Connector to SMA Coax Adapter: https://amzn.to/2gajpAh Screwdriver and pliers (or similar tool) for adjusting fittings (Optional. My node uses this, but a roof mount is a better permanent option) 3 Ft Satellite Tripod: https://amzn.to/2w81RZm Other requirements: Smartphone satellite alignment app and/or compass Patience, some elbow grease, and the will to learn! Hardware assembly: Note: Before you mount the dish assembly to the tripod, make absolutely sure the tripod is level. If the tripod is not level, you will run into difficulties when aligning the dish. This image should give you a pretty good idea of how the assembly goes, sans the LNB part. We have a different LNB and LNB mounting bracket which is mounted slightly different than pictured here. The tripod requires no assembly and simply unfolds. ![1_0vsWGWSbcA4nPxH5CCb4JQ.jpg](https://cdn.steemitimages.com/DQmZ8giuDLrc8wcd4XzP3kqnGVsS7u5onwWY7HACdMAw8nC/1_0vsWGWSbcA4nPxH5CCb4JQ.jpg) Adjusting the tripod’s mast mount fittings: You can fine-tune the tripod and mast’s level with the six screws pictured here (the two not-visible fittings are on the opposite side). Mine came with a bubble-level that fits on the top of the mast. A smartphone app might also work. ![1_Q2jt9PfBh5OuQnmOyxDUnw.png](https://cdn.steemitimages.com/DQmeBQZ1itEzE9m1f7YCyvvfBjJbSfCbGytYZttmFT9VRW9/1_Q2jt9PfBh5OuQnmOyxDUnw.png) Fit the dish assembly to the tripod mast: There are two bolts used to secure the dish assembly to the tripod mast, and two bolts (one shown, one on other side) used to secure the dish assembly’s elevation. Tighten all of the bolts enough to hold their position, but be able to be adjusted with a fair amount of physical effort in order for you to fine-tune the dish assembly’s azimuth and elevation. Mounting the LNB bracket to the LNB support arm: Mount the bracket on the top of the support arm and make sure it is center-aligned and not skewed left or right. Mount the LNB onto the LNB bracket as shown, but keep the screws semi-loose to allow you to adjust the LNB’s polarity while aligning. You can go ahead and connect the coax cable to the LNB at this point if you want. ![1_lr1M_rh5qy1zFa2FqEgnRw.jpg](https://cdn.steemitimages.com/DQmWUQsfDJUESSmS83AzKLzn1iTCg94femG2bsT7gEh8KYx/1_lr1M_rh5qy1zFa2FqEgnRw.jpg) Connecting the cabling: Refer to my attempt at a simple cabling chart to help you connect the SDR to the LNB power supply using the SMA to F adapter cable, and the LNB to the LNB power supply with the coaxial cable. Your power supply may have different labeling for the connections. If you attach the SDR to the wrong connection, you may damage the SDR. Make sure to research your own LNB power supply to know for sure where to connect everything. ![1_ckjJ2LstRfnoWTlu2DYTZw.png](https://cdn.steemitimages.com/DQmYTKLxTDLv4hbZsovJuocdujEXLLhxVyPpdQKrP6jB6a7/1_ckjJ2LstRfnoWTlu2DYTZw.png) This concludes Part 1 — Hardware Assembly. Part 2 will focus on installing the necessary software to receive blocks from Blockstream Satellites. Part 3 will consist of using Gnuradio to align your dish and start receiving blocks! A special thanks to Chris Cook at Blockstream for walking me through setting my sat node up, and also to Greg Maxwell for informing me of such a cool and exciting application of technology. For a more in-depth guide visit: https://github.com/Blockstream/satellite
json metadata{"tags":["steem"],"image":["https://cdn.steemitimages.com/DQmXt1HjrFHA7bH14UbrdNApwZtpAtf2z2MkSiabk19w9pm/1_gN909Ok7Ei98Fdl-Zx94NQ.png","https://cdn.steemitimages.com/DQmZ8giuDLrc8wcd4XzP3kqnGVsS7u5onwWY7HACdMAw8nC/1_0vsWGWSbcA4nPxH5CCb4JQ.jpg","https://cdn.steemitimages.com/DQmeBQZ1itEzE9m1f7YCyvvfBjJbSfCbGytYZttmFT9VRW9/1_Q2jt9PfBh5OuQnmOyxDUnw.png","https://cdn.steemitimages.com/DQmWUQsfDJUESSmS83AzKLzn1iTCg94femG2bsT7gEh8KYx/1_lr1M_rh5qy1zFa2FqEgnRw.jpg","https://cdn.steemitimages.com/DQmYTKLxTDLv4hbZsovJuocdujEXLLhxVyPpdQKrP6jB6a7/1_ckjJ2LstRfnoWTlu2DYTZw.png"],"links":["https://amzn.to/2x6G86r","https://amzn.to/2wBtPzK","https://amzn.to/2g8Nu2O","https://amzn.to/2w0Zk4C","https://amzn.to/2xgotXU","https://amzn.to/2KUGouq","https://amzn.to/2w7N4xQ","https://amzn.to/2gajpAh","https://amzn.to/2w81RZm","https://github.com/Blockstream/satellite"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #36881514/Trx 55e997bb83b8fae2265242217be4d9d6448537d8
View Raw JSON Data
{
  "trx_id": "55e997bb83b8fae2265242217be4d9d6448537d8",
  "block": 36881514,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-30T18:44:57",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "steem",
      "author": "alwaysnew",
      "permlink": "building-your-own-bitcoin-satellite-node",
      "title": "Building Your Own Bitcoin Satellite Node",
      "body": "![1_gN909Ok7Ei98Fdl-Zx94NQ.png](https://cdn.steemitimages.com/DQmXt1HjrFHA7bH14UbrdNApwZtpAtf2z2MkSiabk19w9pm/1_gN909Ok7Ei98Fdl-Zx94NQ.png)\n\n\nHardware requirements:\nNote: The Amazon affiliate links are just to show what parts to get. You can undoubtedly find the parts on eBay if you want to. I realize some of the parts may be sold out on Amazon at this time. This guide was written for the parts on this list.\n\nA computer with Linux installed. This guide uses Fedora 26. I went with Fedora because it is free, it is compatible with the software required, and because it has a large user base. Make sure to have an i5 or a similarly performant processor: https://amzn.to/2x6G86r\nNote: It is now possible to run the Satellite receiver software on a Raspberry Pi or similar device! If using Ubuntu or another Debian-based distro, you can just add the PPA and apt install satellite !\n\nAmple storage space (roughly 4GB for a pruned node, 150GB+ for non-pruned)\nAt least a 46cm (18\") satellite dish: https://amzn.to/2wBtPzK\nSoftware Defined Radio Interface: https://amzn.to/2g8Nu2O\nLinear Polarization PLL LNB: https://amzn.to/2w0Zk4C\nLNB Mounting Bracket: https://amzn.to/2xgotXU\nLNB Power Supply: https://amzn.to/2KUGouq\nCoax Cable: https://amzn.to/2w7N4xQ\nF Connector to SMA Coax Adapter: https://amzn.to/2gajpAh\nScrewdriver and pliers (or similar tool) for adjusting fittings\n(Optional. My node uses this, but a roof mount is a better permanent option) 3 Ft Satellite Tripod: https://amzn.to/2w81RZm\nOther requirements:\nSmartphone satellite alignment app and/or compass\nPatience, some elbow grease, and the will to learn!\nHardware assembly:\nNote: Before you mount the dish assembly to the tripod, make absolutely sure the tripod is level. If the tripod is not level, you will run into difficulties when aligning the dish.\n\nThis image should give you a pretty good idea of how the assembly goes, sans the LNB part. We have a different LNB and LNB mounting bracket which is mounted slightly different than pictured here. The tripod requires no assembly and simply unfolds.\n\n\n![1_0vsWGWSbcA4nPxH5CCb4JQ.jpg](https://cdn.steemitimages.com/DQmZ8giuDLrc8wcd4XzP3kqnGVsS7u5onwWY7HACdMAw8nC/1_0vsWGWSbcA4nPxH5CCb4JQ.jpg)\n\nAdjusting the tripod’s mast mount fittings:\nYou can fine-tune the tripod and mast’s level with the six screws pictured here (the two not-visible fittings are on the opposite side). Mine came with a bubble-level that fits on the top of the mast. A smartphone app might also work.\n\n![1_Q2jt9PfBh5OuQnmOyxDUnw.png](https://cdn.steemitimages.com/DQmeBQZ1itEzE9m1f7YCyvvfBjJbSfCbGytYZttmFT9VRW9/1_Q2jt9PfBh5OuQnmOyxDUnw.png)\n\n\nFit the dish assembly to the tripod mast:\nThere are two bolts used to secure the dish assembly to the tripod mast, and two bolts (one shown, one on other side) used to secure the dish assembly’s elevation. Tighten all of the bolts enough to hold their position, but be able to be adjusted with a fair amount of physical effort in order for you to fine-tune the dish assembly’s azimuth and elevation.\n\nMounting the LNB bracket to the LNB support arm:\nMount the bracket on the top of the support arm and make sure it is center-aligned and not skewed left or right. Mount the LNB onto the LNB bracket as shown, but keep the screws semi-loose to allow you to adjust the LNB’s polarity while aligning. You can go ahead and connect the coax cable to the LNB at this point if you want.\n\n\n![1_lr1M_rh5qy1zFa2FqEgnRw.jpg](https://cdn.steemitimages.com/DQmWUQsfDJUESSmS83AzKLzn1iTCg94femG2bsT7gEh8KYx/1_lr1M_rh5qy1zFa2FqEgnRw.jpg)\n\n\nConnecting the cabling:\nRefer to my attempt at a simple cabling chart to help you connect the SDR to the LNB power supply using the SMA to F adapter cable, and the LNB to the LNB power supply with the coaxial cable. Your power supply may have different labeling for the connections. If you attach the SDR to the wrong connection, you may damage the SDR. Make sure to research your own LNB power supply to know for sure where to connect everything.\n\n![1_ckjJ2LstRfnoWTlu2DYTZw.png](https://cdn.steemitimages.com/DQmYTKLxTDLv4hbZsovJuocdujEXLLhxVyPpdQKrP6jB6a7/1_ckjJ2LstRfnoWTlu2DYTZw.png)\n\n\nThis concludes Part 1 — Hardware Assembly. Part 2 will focus on installing the necessary software to receive blocks from Blockstream Satellites. Part 3 will consist of using Gnuradio to align your dish and start receiving blocks!\n\nA special thanks to Chris Cook at Blockstream for walking me through setting my sat node up, and also to Greg Maxwell for informing me of such a cool and exciting application of technology.\n\nFor a more in-depth guide visit: https://github.com/Blockstream/satellite",
      "json_metadata": "{\"tags\":[\"steem\"],\"image\":[\"https://cdn.steemitimages.com/DQmXt1HjrFHA7bH14UbrdNApwZtpAtf2z2MkSiabk19w9pm/1_gN909Ok7Ei98Fdl-Zx94NQ.png\",\"https://cdn.steemitimages.com/DQmZ8giuDLrc8wcd4XzP3kqnGVsS7u5onwWY7HACdMAw8nC/1_0vsWGWSbcA4nPxH5CCb4JQ.jpg\",\"https://cdn.steemitimages.com/DQmeBQZ1itEzE9m1f7YCyvvfBjJbSfCbGytYZttmFT9VRW9/1_Q2jt9PfBh5OuQnmOyxDUnw.png\",\"https://cdn.steemitimages.com/DQmWUQsfDJUESSmS83AzKLzn1iTCg94femG2bsT7gEh8KYx/1_lr1M_rh5qy1zFa2FqEgnRw.jpg\",\"https://cdn.steemitimages.com/DQmYTKLxTDLv4hbZsovJuocdujEXLLhxVyPpdQKrP6jB6a7/1_ckjJ2LstRfnoWTlu2DYTZw.png\"],\"links\":[\"https://amzn.to/2x6G86r\",\"https://amzn.to/2wBtPzK\",\"https://amzn.to/2g8Nu2O\",\"https://amzn.to/2w0Zk4C\",\"https://amzn.to/2xgotXU\",\"https://amzn.to/2KUGouq\",\"https://amzn.to/2w7N4xQ\",\"https://amzn.to/2gajpAh\",\"https://amzn.to/2w81RZm\",\"https://github.com/Blockstream/satellite\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2019/09/28 19:31:09
voterfilipino
authoralwaysnew
permlinkfractal-dimension
weight1000 (10.00%)
Transaction InfoBlock #36824959/Trx 9bf172e11b4be5ab5b65a06d1ccb74bc823946bd
View Raw JSON Data
{
  "trx_id": "9bf172e11b4be5ab5b65a06d1ccb74bc823946bd",
  "block": 36824959,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-28T19:31:09",
  "op": [
    "vote",
    {
      "voter": "filipino",
      "author": "alwaysnew",
      "permlink": "fractal-dimension",
      "weight": 1000
    }
  ]
}
2019/09/28 18:50:42
parent authoralwaysnew
parent permlinkfractal-dimension
authorcheetah
permlinkcheetah-re-alwaysnewfractal-dimension
title
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://en.wikipedia.org/wiki/Fractal_dimension
json metadata
Transaction InfoBlock #36824152/Trx ec4b8487e80043166fb957d7134772b68d2b63e3
View Raw JSON Data
{
  "trx_id": "ec4b8487e80043166fb957d7134772b68d2b63e3",
  "block": 36824152,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-28T18:50:42",
  "op": [
    "comment",
    {
      "parent_author": "alwaysnew",
      "parent_permlink": "fractal-dimension",
      "author": "cheetah",
      "permlink": "cheetah-re-alwaysnewfractal-dimension",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://en.wikipedia.org/wiki/Fractal_dimension",
      "json_metadata": ""
    }
  ]
}
2019/09/28 18:50:36
votercheetah
authoralwaysnew
permlinkfractal-dimension
weight8 (0.08%)
Transaction InfoBlock #36824150/Trx 27d6ad18fc05db2da0b5a3b10937e7ac27f5084b
View Raw JSON Data
{
  "trx_id": "27d6ad18fc05db2da0b5a3b10937e7ac27f5084b",
  "block": 36824150,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-28T18:50:36",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "alwaysnew",
      "permlink": "fractal-dimension",
      "weight": 8
    }
  ]
}
alwaysnewpublished a new post: fractal-dimension
2019/09/28 18:50:18
parent author
parent permlinksteem
authoralwaysnew
permlinkfractal-dimension
titleFractal dimension
bodyIn mathematics, more specifically in fractal geometry, a fractal dimension is a ratio providing a statistical index of complexity comparing how detail in a pattern (strictly speaking, a fractal pattern) changes with the scale at which it is measured. It has also been characterized as a measure of the space-filling capacity of a pattern that tells how a fractal scales differently from the space it is embedded in; a fractal dimension does not have to be an integer.[1][2][3] The essential idea of "fractured" dimensions has a long history in mathematics, but the term itself was brought to the fore by Benoit Mandelbrot based on his 1967 paper on self-similarity in which he discussed fractional dimensions.[4] In that paper, Mandelbrot cited previous work by Lewis Fry Richardson describing the counter-intuitive notion that a coastline's measured length changes with the length of the measuring stick used (see Fig. 1). In terms of that notion, the fractal dimension of a coastline quantifies how the number of scaled measuring sticks required to measure the coastline changes with the scale applied to the stick.[5] There are several formal mathematical definitions of fractal dimension that build on this basic concept of change in detail with change in scale. Ultimately, the term fractal dimension became the phrase with which Mandelbrot himself became most comfortable with respect to encapsulating the meaning of the word fractal, a term he created. After several iterations over years, Mandelbrot settled on this use of the language: "...to use fractal without a pedantic definition, to use fractal dimension as a generic term applicable to all the variants."[6] One non-trivial example is the fractal dimension of a Koch snowflake. It has a topological dimension of 1, but it is by no means a rectifiable curve: the length of the curve between any two points on the Koch snowflake is infinite. No small piece of it is line-like, but rather it is composed of an infinite number of segments joined at different angles. The fractal dimension of a curve can be explained intuitively thinking of a fractal line as an object too detailed to be one-dimensional, but too simple to be two-dimensional.[7] Therefore its dimension might best be described not by its usual topological dimension of 1 but by its fractal dimension, which is often a number between one and two; in the case of the Koch snowflake, it is about 1.262. Introduction Figure 2. A 32-segment quadric fractal scaled and viewed through boxes of different sizes. The pattern illustrates self similarity. The theoretical fractal dimension for this fractal is log32/log8 = 1.67; its empirical fractal dimension from box counting analysis is ±1%[8] using fractal analysis software. A fractal dimension is an index for characterizing fractal patterns or sets by quantifying their complexity as a ratio of the change in detail to the change in scale.[5]:1 Several types of fractal dimension can be measured theoretically and empirically (see Fig. 2).[3][9] Fractal dimensions are used to characterize a broad spectrum of objects ranging from the abstract[1][3] to practical phenomena, including turbulence,[5]:97–104 river networks,:246–247 urban growth,[10][11] human physiology,[12][13] medicine,[9] and market trends.[14] The essential idea of fractional or fractal dimensions has a long history in mathematics that can be traced back to the 1600s,[5]:19[15] but the terms fractal and fractal dimension were coined by mathematician Benoit Mandelbrot in 1975.[1][2][5][9][14][16] Fractal dimensions were first applied as an index characterizing complicated geometric forms for which the details seemed more important than the gross picture.[16] For sets describing ordinary geometric shapes, the theoretical fractal dimension equals the set's familiar Euclidean or topological dimension. Thus, it is 0 for sets describing points (0-dimensional sets); 1 for sets describing lines (1-dimensional sets having length only); 2 for sets describing surfaces (2-dimensional sets having length and width); and 3 for sets describing volumes (3-dimensional sets having length, width, and height). But this changes for fractal sets. If the theoretical fractal dimension of a set exceeds its topological dimension, the set is considered to have fractal geometry.[17] Unlike topological dimensions, the fractal index can take non-integer values,[18] indicating that a set fills its space qualitatively and quantitatively differently from how an ordinary geometrical set does.[1][2][3] For instance, a curve with a fractal dimension very near to 1, say 1.10, behaves quite like an ordinary line, but a curve with fractal dimension 1.9 winds convolutedly through space very nearly like a surface. Similarly, a surface with fractal dimension of 2.1 fills space very much like an ordinary surface, but one with a fractal dimension of 2.9 folds and flows to fill space rather nearly like a volume.[17]:48[notes 1] This general relationship can be seen in the two images of fractal curves in Fig.2 and Fig. 3 – the 32-segment contour in Fig. 2, convoluted and space filling, has a fractal dimension of 1.67, compared to the perceptibly less complex Koch curve in Fig. 3, which has a fractal dimension of 1.26. a Koch curve animation Figure 3. The Koch curve is a classic iterated fractal curve. It is a theoretical construct that is made by iteratively scaling a starting segment. As shown, each new segment is scaled by 1/3 into 4 new pieces laid end to end with 2 middle pieces leaning toward each other between the other two pieces, so that if they were a triangle its base would be the length of the middle piece, so that the whole new segment fits across the traditionally measured length between the endpoints of the previous segment. Whereas the animation only shows a few iterations, the theoretical curve is scaled in this way infinitely. Beyond about 6 iterations on an image this small, the detail is lost. The relationship of an increasing fractal dimension with space-filling might be taken to mean fractal dimensions measure density, but that is not so; the two are not strictly correlated.[8] Instead, a fractal dimension measures complexity, a concept related to certain key features of fractals: self-similarity and detail or irregularity.[notes 2] These features are evident in the two examples of fractal curves. Both are curves with topological dimension of 1, so one might hope to be able to measure their length or slope, as with ordinary lines. But we cannot do either of these things, because fractal curves have complexity in the form of self-similarity and detail that ordinary lines lack.[5] The self-similarity lies in the infinite scaling, and the detail in the defining elements of each set. The length between any two points on these curves is undefined because the curves are theoretical constructs that never stop repeating themselves.[19] Every smaller piece is composed of an infinite number of scaled segments that look exactly like the first iteration. These are not rectifiable curves, meaning they cannot be measured by being broken down into many segments approximating their respective lengths. They cannot be characterized by finding their lengths or slopes. However, their fractal dimensions can be determined, which shows that both fill space more than ordinary lines but less than surfaces, and allows them to be compared in this regard. The two fractal curves described above show a type of self-similarity that is exact with a repeating unit of detail that is readily visualized. This sort of structure can be extended to other spaces (e.g., a fractal that extends the Koch curve into 3-d space has a theoretical D=2.5849). However, such neatly countable complexity is only one example of the self-similarity and detail that are present in fractals.[3][14] The example of the coast line of Britain, for instance, exhibits self-similarity of an approximate pattern with approximate scaling.[5]:26 Overall, fractals show several types and degrees of self-similarity and detail that may not be easily visualized. These include, as examples, strange attractors for which the detail has been described as in essence, smooth portions piling up,[17]:49 the Julia set, which can be seen to be complex swirls upon swirls, and heart rates, which are patterns of rough spikes repeated and scaled in time.[20] Fractal complexity may not always be resolvable into easily grasped units of detail and scale without complex analytic methods but it is still quantifiable through fractal dimensions.[5]:197; 262 History The terms fractal dimension and fractal were coined by Mandelbrot in 1975,[16] about a decade after he published his paper on self-similarity in the coastline of Britain. Various historical authorities credit him with also synthesizing centuries of complicated theoretical mathematics and engineering work and applying them in a new way to study complex geometries that defied description in usual linear terms.[15][21][22] The earliest roots of what Mandelbrot synthesized as the fractal dimension have been traced clearly back to writings about undifferentiable, infinitely self-similar functions, which are important in the mathematical definition of fractals, around the time that calculus was discovered in the mid-1600s.[5]:405 There was a lull in the published work on such functions for a time after that, then a renewal starting in the late 1800s with the publishing of mathematical functions and sets that are today called canonical fractals (such as the eponymous works of von Koch,[19] Sierpiński, and Julia), but at the time of their formulation were often considered antithetical mathematical "monsters".[15][22] These works were accompanied by perhaps the most pivotal point in the development of the concept of a fractal dimension through the work of Hausdorff in the early 1900s who defined a "fractional" dimension that has come to be named after him and is frequently invoked in defining modern fractals.[4][5]:44[17][21] See Fractal history for more information Role of scaling Lines, squares, and cubes. Figure 4. Traditional notions of geometry for defining scaling and dimension. The concept of a fractal dimension rests in unconventional views of scaling and dimension.[23] As Fig. 4 illustrates, traditional notions of geometry dictate that shapes scale predictably according to intuitive and familiar ideas about the space they are contained within, such that, for instance, measuring a line using first one measuring stick then another 1/3 its size, will give for the second stick a total length 3 times as many sticks long as with the first. This holds in 2 dimensions, as well. If one measures the area of a square then measures again with a box of side length 1/3 the size of the original, one will find 9 times as many squares as with the first measure. Such familiar scaling relationships can be defined mathematically by the general scaling rule in Equation 1, where the variable {\displaystyle N}N stands for the number of sticks, {\displaystyle \varepsilon }\varepsilon for the scaling factor, and {\displaystyle D}D for the fractal dimension: {\displaystyle {N\propto \varepsilon ^{-D}},}{\displaystyle {N\propto \varepsilon ^{-D}},} (1) where {\displaystyle \propto }\propto denotes proportionality. This scaling rule typifies conventional rules about geometry and dimension – for lines, it quantifies that, because {\displaystyle N=3}N=3 when {\displaystyle \varepsilon ={\tfrac {1}{3}}}{\displaystyle \varepsilon ={\tfrac {1}{3}}} as in the example above, {\displaystyle D=1,}{\displaystyle D=1,} and for squares, because {\displaystyle N=9}{\displaystyle N=9} when {\displaystyle \varepsilon ={\tfrac {1}{3}},D=2.}{\displaystyle \varepsilon ={\tfrac {1}{3}},D=2.} A fractal contour of a koch snowflake Figure 5. The first four iterations of the Koch snowflake, which has an approximate Hausdorff dimension of 1.2619. The same rule applies to fractal geometry but less intuitively. To elaborate, a fractal line measured at first to be one length, when remeasured using a new stick scaled by 1/3 of the old may not be the expected 3 but instead 4 times as many scaled sticks long. In this case, {\displaystyle N=4}N=4 when {\displaystyle \varepsilon ={\tfrac {1}{3}},}{\displaystyle \varepsilon ={\tfrac {1}{3}},} and the value of {\displaystyle D}D can be found by rearranging Equation 1: {\displaystyle {\log _{\varepsilon }{N}={-D}={\frac {\log {N}}{\log {\varepsilon }}}}}{\displaystyle {\log _{\varepsilon }{N}={-D}={\frac {\log {N}}{\log {\varepsilon }}}}} (2) That is, for a fractal described by {\displaystyle N=4}N=4 when {\displaystyle \varepsilon ={\tfrac {1}{3}},D=1.2619,}{\displaystyle \varepsilon ={\tfrac {1}{3}},D=1.2619,} a non-integer dimension that suggests the fractal has a dimension not equal to the space it resides in.[3] The scaling used in this example is the same scaling of the Koch curve and snowflake. Of note, the images shown are not true fractals because the scaling described by the value of {\displaystyle D}D cannot continue infinitely for the simple reason that the images only exist to the point of their smallest component, a pixel. The theoretical pattern that the digital images represent, however, has no discrete pixel-like pieces, but rather is composed of an infinite number of infinitely scaled segments joined at different angles and does indeed have a fractal dimension of 1.2619.[5][23] D is not a unique descriptor Figure 6. Two L-systems branching fractals that are made by producing 4 new parts for every 1/3 scaling so have the same theoretical {\displaystyle D}D as the Koch curve and for which the empirical box counting {\displaystyle D}D has been demonstrated with 2% accuracy.[8] As is the case with dimensions determined for lines, squares, and cubes, fractal dimensions are general descriptors that do not uniquely define patterns.[23][24] The value of D for the Koch fractal discussed above, for instance, quantifies the pattern's inherent scaling, but does not uniquely describe nor provide enough information to reconstruct it. Many fractal structures or patterns could be constructed that have the same scaling relationship but are dramatically different from the Koch curve, as is illustrated in Figure 6. For examples of how fractal patterns can be constructed, see Fractal, Sierpinski triangle, Mandelbrot set, Diffusion limited aggregation, L-System. Fractal surface structures The concept of fractality is applied increasingly in the field of surface science, providing a bridge between surface characteristics and functional properties.[25] Numerous surface descriptors are used to interpret the structure of nominally flat surfaces, which often exhibit self-affine features across multiple length-scales. Mean surface roughness, usually denoted RA, is the most commonly applied surface descriptor, however numerous other descriptors including mean slope, root mean square roughness (RRMS) and others are regularly applied. It is found however that many physical surface phenomena cannot readily be interpreted with reference to such descriptors, thus fractal dimension is increasingly applied to establish correlations between surface structure in terms of scaling behavior and performance.[26] The fractal dimensions of surfaces have been employed to explain and better understand phenomena in areas of contact mechanics,[27] frictional behavior,[28] electrical contact resistance[29] and transparent conducting oxides.[30] Figure 7: Illustration of increasing surface fractality. Self-affine surfaces (left) and corresponding surface profiles (right) showing increasing fractal dimension Df Examples The concept of fractal dimension described in this article is a basic view of a complicated construct. The examples discussed here were chosen for clarity, and the scaling unit and ratios were known ahead of time. In practice, however, fractal dimensions can be determined using techniques that approximate scaling and detail from limits estimated from regression lines over log vs log plots of size vs scale. Several formal mathematical definitions of different types of fractal dimension are listed below. Although for some classic fractals all these dimensions coincide, in general they are not equivalent: Box counting dimension: D is estimated as the exponent of a power law. {\displaystyle D_{0}=\lim _{\varepsilon \to 0}{\frac {\log N(\varepsilon )}{\log {\frac {1}{\varepsilon }}}}.}{\displaystyle D_{0}=\lim _{\varepsilon \to 0}{\frac {\log N(\varepsilon )}{\log {\frac {1}{\varepsilon }}}}.} Information dimension: D considers how the average information needed to identify an occupied box scales with box size; {\displaystyle p}p is a probability. {\displaystyle D_{1}=\lim _{\varepsilon \to 0}{\frac {-\langle \log p_{\varepsilon }\rangle }{\log {\frac {1}{\varepsilon }}}}}{\displaystyle D_{1}=\lim _{\varepsilon \to 0}{\frac {-\langle \log p_{\varepsilon }\rangle }{\log {\frac {1}{\varepsilon }}}}} Correlation dimension: D is based on {\displaystyle M}M as the number of points used to generate a representation of a fractal and gε, the number of pairs of points closer than ε to each other. {\displaystyle D_{2}=\lim _{M\to \infty }\lim _{\varepsilon \to 0}{\frac {\log(g_{\varepsilon }/M^{2})}{\log \varepsilon }}}{\displaystyle D_{2}=\lim _{M\to \infty }\lim _{\varepsilon \to 0}{\frac {\log(g_{\varepsilon }/M^{2})}{\log \varepsilon }}}[citation needed] Generalized or Rényi dimensions: The box-counting, information, and correlation dimensions can be seen as special cases of a continuous spectrum of generalized dimensions of order α, defined by: {\displaystyle D_{\alpha }=\lim _{\varepsilon \to 0}{\frac {{\frac {1}{\alpha -1}}\log(\sum _{i}p_{i}^{\alpha })}{\log \varepsilon }}}{\displaystyle D_{\alpha }=\lim _{\varepsilon \to 0}{\frac {{\frac {1}{\alpha -1}}\log(\sum _{i}p_{i}^{\alpha })}{\log \varepsilon }}} Higuchi dimension[31] {\displaystyle D={\frac {d\ \log(L(k))}{d\ \log(k)}}}D={\frac {d\ \log(L(k))}{d\ \log(k)}} Lyapunov dimension Multifractal dimensions: a special case of Rényi dimensions where scaling behaviour varies in different parts of the pattern. Uncertainty exponent Hausdorff dimension: For any subset {\displaystyle S}S of a metric space {\displaystyle X}X and {\displaystyle d\geq 0}{\displaystyle d\geq 0}, the d-dimensional Hausdorff content of S is defined by {\displaystyle C_{H}^{d}(S):=\inf {\Bigl \{}\sum _{i}r_{i}^{d}:{\text{ there is a cover of }}S{\text{ by balls with radii }}r_{i}>0{\Bigr \}}.}C_H^d(S):=\inf\Bigl\{\sum_i r_i^d:\text{ there is a cover of } S\text{ by balls with radii }r_i>0\Bigr\}. The Hausdorff dimension of S is defined by {\displaystyle \dim _{\operatorname {H} }(X):=\inf\{d\geq 0:C_{H}^{d}(X)=0\}.}\dim _{{\operatorname {H}}}(X):=\inf\{d\geq 0:C_{H}^{d}(X)=0\}.
json metadata{"tags":["steem"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #36824144/Trx bb9caa915c50ca5a8c558802b1abc3aec52063f4
View Raw JSON Data
{
  "trx_id": "bb9caa915c50ca5a8c558802b1abc3aec52063f4",
  "block": 36824144,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-28T18:50:18",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "steem",
      "author": "alwaysnew",
      "permlink": "fractal-dimension",
      "title": "Fractal dimension",
      "body": "In mathematics, more specifically in fractal geometry, a fractal dimension is a ratio providing a statistical index of complexity comparing how detail in a pattern (strictly speaking, a fractal pattern) changes with the scale at which it is measured. It has also been characterized as a measure of the space-filling capacity of a pattern that tells how a fractal scales differently from the space it is embedded in; a fractal dimension does not have to be an integer.[1][2][3]\n\nThe essential idea of \"fractured\" dimensions has a long history in mathematics, but the term itself was brought to the fore by Benoit Mandelbrot based on his 1967 paper on self-similarity in which he discussed fractional dimensions.[4] In that paper, Mandelbrot cited previous work by Lewis Fry Richardson describing the counter-intuitive notion that a coastline's measured length changes with the length of the measuring stick used (see Fig. 1). In terms of that notion, the fractal dimension of a coastline quantifies how the number of scaled measuring sticks required to measure the coastline changes with the scale applied to the stick.[5] There are several formal mathematical definitions of fractal dimension that build on this basic concept of change in detail with change in scale.\n\nUltimately, the term fractal dimension became the phrase with which Mandelbrot himself became most comfortable with respect to encapsulating the meaning of the word fractal, a term he created. After several iterations over years, Mandelbrot settled on this use of the language: \"...to use fractal without a pedantic definition, to use fractal dimension as a generic term applicable to all the variants.\"[6]\n\nOne non-trivial example is the fractal dimension of a Koch snowflake. It has a topological dimension of 1, but it is by no means a rectifiable curve: the length of the curve between any two points on the Koch snowflake is infinite. No small piece of it is line-like, but rather it is composed of an infinite number of segments joined at different angles. The fractal dimension of a curve can be explained intuitively thinking of a fractal line as an object too detailed to be one-dimensional, but too simple to be two-dimensional.[7] Therefore its dimension might best be described not by its usual topological dimension of 1 but by its fractal dimension, which is often a number between one and two; in the case of the Koch snowflake, it is about 1.262.\n\nIntroduction\n\n\nFigure 2. A 32-segment quadric fractal scaled and viewed through boxes of different sizes. The pattern illustrates self similarity. The theoretical fractal dimension for this fractal is log32/log8 = 1.67; its empirical fractal dimension from box counting analysis is ±1%[8] using fractal analysis software.\nA fractal dimension is an index for characterizing fractal patterns or sets by quantifying their complexity as a ratio of the change in detail to the change in scale.[5]:1 Several types of fractal dimension can be measured theoretically and empirically (see Fig. 2).[3][9] Fractal dimensions are used to characterize a broad spectrum of objects ranging from the abstract[1][3] to practical phenomena, including turbulence,[5]:97–104 river networks,:246–247 urban growth,[10][11] human physiology,[12][13] medicine,[9] and market trends.[14] The essential idea of fractional or fractal dimensions has a long history in mathematics that can be traced back to the 1600s,[5]:19[15] but the terms fractal and fractal dimension were coined by mathematician Benoit Mandelbrot in 1975.[1][2][5][9][14][16]\n\nFractal dimensions were first applied as an index characterizing complicated geometric forms for which the details seemed more important than the gross picture.[16] For sets describing ordinary geometric shapes, the theoretical fractal dimension equals the set's familiar Euclidean or topological dimension. Thus, it is 0 for sets describing points (0-dimensional sets); 1 for sets describing lines (1-dimensional sets having length only); 2 for sets describing surfaces (2-dimensional sets having length and width); and 3 for sets describing volumes (3-dimensional sets having length, width, and height). But this changes for fractal sets. If the theoretical fractal dimension of a set exceeds its topological dimension, the set is considered to have fractal geometry.[17]\n\nUnlike topological dimensions, the fractal index can take non-integer values,[18] indicating that a set fills its space qualitatively and quantitatively differently from how an ordinary geometrical set does.[1][2][3] For instance, a curve with a fractal dimension very near to 1, say 1.10, behaves quite like an ordinary line, but a curve with fractal dimension 1.9 winds convolutedly through space very nearly like a surface. Similarly, a surface with fractal dimension of 2.1 fills space very much like an ordinary surface, but one with a fractal dimension of 2.9 folds and flows to fill space rather nearly like a volume.[17]:48[notes 1] This general relationship can be seen in the two images of fractal curves in Fig.2 and Fig. 3 – the 32-segment contour in Fig. 2, convoluted and space filling, has a fractal dimension of 1.67, compared to the perceptibly less complex Koch curve in Fig. 3, which has a fractal dimension of 1.26.\n\n\na Koch curve animation\nFigure 3. The Koch curve is a classic iterated fractal curve. It is a theoretical construct that is made by iteratively scaling a starting segment. As shown, each new segment is scaled by 1/3 into 4 new pieces laid end to end with 2 middle pieces leaning toward each other between the other two pieces, so that if they were a triangle its base would be the length of the middle piece, so that the whole new segment fits across the traditionally measured length between the endpoints of the previous segment. Whereas the animation only shows a few iterations, the theoretical curve is scaled in this way infinitely. Beyond about 6 iterations on an image this small, the detail is lost.\nThe relationship of an increasing fractal dimension with space-filling might be taken to mean fractal dimensions measure density, but that is not so; the two are not strictly correlated.[8] Instead, a fractal dimension measures complexity, a concept related to certain key features of fractals: self-similarity and detail or irregularity.[notes 2] These features are evident in the two examples of fractal curves. Both are curves with topological dimension of 1, so one might hope to be able to measure their length or slope, as with ordinary lines. But we cannot do either of these things, because fractal curves have complexity in the form of self-similarity and detail that ordinary lines lack.[5] The self-similarity lies in the infinite scaling, and the detail in the defining elements of each set. The length between any two points on these curves is undefined because the curves are theoretical constructs that never stop repeating themselves.[19] Every smaller piece is composed of an infinite number of scaled segments that look exactly like the first iteration. These are not rectifiable curves, meaning they cannot be measured by being broken down into many segments approximating their respective lengths. They cannot be characterized by finding their lengths or slopes. However, their fractal dimensions can be determined, which shows that both fill space more than ordinary lines but less than surfaces, and allows them to be compared in this regard.\n\nThe two fractal curves described above show a type of self-similarity that is exact with a repeating unit of detail that is readily visualized. This sort of structure can be extended to other spaces (e.g., a fractal that extends the Koch curve into 3-d space has a theoretical D=2.5849). However, such neatly countable complexity is only one example of the self-similarity and detail that are present in fractals.[3][14] The example of the coast line of Britain, for instance, exhibits self-similarity of an approximate pattern with approximate scaling.[5]:26 Overall, fractals show several types and degrees of self-similarity and detail that may not be easily visualized. These include, as examples, strange attractors for which the detail has been described as in essence, smooth portions piling up,[17]:49 the Julia set, which can be seen to be complex swirls upon swirls, and heart rates, which are patterns of rough spikes repeated and scaled in time.[20] Fractal complexity may not always be resolvable into easily grasped units of detail and scale without complex analytic methods but it is still quantifiable through fractal dimensions.[5]:197; 262\n\nHistory\nThe terms fractal dimension and fractal were coined by Mandelbrot in 1975,[16] about a decade after he published his paper on self-similarity in the coastline of Britain. Various historical authorities credit him with also synthesizing centuries of complicated theoretical mathematics and engineering work and applying them in a new way to study complex geometries that defied description in usual linear terms.[15][21][22] The earliest roots of what Mandelbrot synthesized as the fractal dimension have been traced clearly back to writings about undifferentiable, infinitely self-similar functions, which are important in the mathematical definition of fractals, around the time that calculus was discovered in the mid-1600s.[5]:405 There was a lull in the published work on such functions for a time after that, then a renewal starting in the late 1800s with the publishing of mathematical functions and sets that are today called canonical fractals (such as the eponymous works of von Koch,[19] Sierpiński, and Julia), but at the time of their formulation were often considered antithetical mathematical \"monsters\".[15][22] These works were accompanied by perhaps the most pivotal point in the development of the concept of a fractal dimension through the work of Hausdorff in the early 1900s who defined a \"fractional\" dimension that has come to be named after him and is frequently invoked in defining modern fractals.[4][5]:44[17][21]\n\nSee Fractal history for more information\n\n\nRole of scaling\n\nLines, squares, and cubes.\nFigure 4. Traditional notions of geometry for defining scaling and dimension.\nThe concept of a fractal dimension rests in unconventional views of scaling and dimension.[23] As Fig. 4 illustrates, traditional notions of geometry dictate that shapes scale predictably according to intuitive and familiar ideas about the space they are contained within, such that, for instance, measuring a line using first one measuring stick then another 1/3 its size, will give for the second stick a total length 3 times as many sticks long as with the first. This holds in 2 dimensions, as well. If one measures the area of a square then measures again with a box of side length 1/3 the size of the original, one will find 9 times as many squares as with the first measure. Such familiar scaling relationships can be defined mathematically by the general scaling rule in Equation 1, where the variable {\\displaystyle N}N stands for the number of sticks, {\\displaystyle \\varepsilon }\\varepsilon  for the scaling factor, and {\\displaystyle D}D for the fractal dimension:\n\n{\\displaystyle {N\\propto \\varepsilon ^{-D}},}{\\displaystyle {N\\propto \\varepsilon ^{-D}},}\n\n \n\n \n\n \n\n \n\n(1)\n\nwhere {\\displaystyle \\propto }\\propto  denotes proportionality. This scaling rule typifies conventional rules about geometry and dimension – for lines, it quantifies that, because {\\displaystyle N=3}N=3 when {\\displaystyle \\varepsilon ={\\tfrac {1}{3}}}{\\displaystyle \\varepsilon ={\\tfrac {1}{3}}} as in the example above, {\\displaystyle D=1,}{\\displaystyle D=1,} and for squares, because {\\displaystyle N=9}{\\displaystyle N=9} when {\\displaystyle \\varepsilon ={\\tfrac {1}{3}},D=2.}{\\displaystyle \\varepsilon ={\\tfrac {1}{3}},D=2.}\n\n\nA fractal contour of a koch snowflake\nFigure 5. The first four iterations of the Koch snowflake, which has an approximate Hausdorff dimension of 1.2619.\nThe same rule applies to fractal geometry but less intuitively. To elaborate, a fractal line measured at first to be one length, when remeasured using a new stick scaled by 1/3 of the old may not be the expected 3 but instead 4 times as many scaled sticks long. In this case, {\\displaystyle N=4}N=4 when {\\displaystyle \\varepsilon ={\\tfrac {1}{3}},}{\\displaystyle \\varepsilon ={\\tfrac {1}{3}},} and the value of {\\displaystyle D}D can be found by rearranging Equation 1:\n\n{\\displaystyle {\\log _{\\varepsilon }{N}={-D}={\\frac {\\log {N}}{\\log {\\varepsilon }}}}}{\\displaystyle {\\log _{\\varepsilon }{N}={-D}={\\frac {\\log {N}}{\\log {\\varepsilon }}}}}\n\n \n\n \n\n \n\n \n\n(2)\n\nThat is, for a fractal described by {\\displaystyle N=4}N=4 when {\\displaystyle \\varepsilon ={\\tfrac {1}{3}},D=1.2619,}{\\displaystyle \\varepsilon ={\\tfrac {1}{3}},D=1.2619,} a non-integer dimension that suggests the fractal has a dimension not equal to the space it resides in.[3] The scaling used in this example is the same scaling of the Koch curve and snowflake. Of note, the images shown are not true fractals because the scaling described by the value of {\\displaystyle D}D cannot continue infinitely for the simple reason that the images only exist to the point of their smallest component, a pixel. The theoretical pattern that the digital images represent, however, has no discrete pixel-like pieces, but rather is composed of an infinite number of infinitely scaled segments joined at different angles and does indeed have a fractal dimension of 1.2619.[5][23]\n\nD is not a unique descriptor\n\n\nFigure 6. Two L-systems branching fractals that are made by producing 4 new parts for every 1/3 scaling so have the same theoretical {\\displaystyle D}D as the Koch curve and for which the empirical box counting {\\displaystyle D}D has been demonstrated with 2% accuracy.[8]\nAs is the case with dimensions determined for lines, squares, and cubes, fractal dimensions are general descriptors that do not uniquely define patterns.[23][24] The value of D for the Koch fractal discussed above, for instance, quantifies the pattern's inherent scaling, but does not uniquely describe nor provide enough information to reconstruct it. Many fractal structures or patterns could be constructed that have the same scaling relationship but are dramatically different from the Koch curve, as is illustrated in Figure 6.\n\nFor examples of how fractal patterns can be constructed, see Fractal, Sierpinski triangle, Mandelbrot set, Diffusion limited aggregation, L-System.\n\n\nFractal surface structures\nThe concept of fractality is applied increasingly in the field of surface science, providing a bridge between surface characteristics and functional properties.[25] Numerous surface descriptors are used to interpret the structure of nominally flat surfaces, which often exhibit self-affine features across multiple length-scales. Mean surface roughness, usually denoted RA, is the most commonly applied surface descriptor, however numerous other descriptors including mean slope, root mean square roughness (RRMS) and others are regularly applied. It is found however that many physical surface phenomena cannot readily be interpreted with reference to such descriptors, thus fractal dimension is increasingly applied to establish correlations between surface structure in terms of scaling behavior and performance.[26] The fractal dimensions of surfaces have been employed to explain and better understand phenomena in areas of contact mechanics,[27] frictional behavior,[28] electrical contact resistance[29] and transparent conducting oxides.[30]\n\n\nFigure 7: Illustration of increasing surface fractality. Self-affine surfaces (left) and corresponding surface profiles (right) showing increasing fractal dimension Df\nExamples\nThe concept of fractal dimension described in this article is a basic view of a complicated construct. The examples discussed here were chosen for clarity, and the scaling unit and ratios were known ahead of time. In practice, however, fractal dimensions can be determined using techniques that approximate scaling and detail from limits estimated from regression lines over log vs log plots of size vs scale. Several formal mathematical definitions of different types of fractal dimension are listed below. Although for some classic fractals all these dimensions coincide, in general they are not equivalent:\n\nBox counting dimension: D is estimated as the exponent of a power law.\n{\\displaystyle D_{0}=\\lim _{\\varepsilon \\to 0}{\\frac {\\log N(\\varepsilon )}{\\log {\\frac {1}{\\varepsilon }}}}.}{\\displaystyle D_{0}=\\lim _{\\varepsilon \\to 0}{\\frac {\\log N(\\varepsilon )}{\\log {\\frac {1}{\\varepsilon }}}}.}\nInformation dimension: D considers how the average information needed to identify an occupied box scales with box size; {\\displaystyle p}p is a probability.\n{\\displaystyle D_{1}=\\lim _{\\varepsilon \\to 0}{\\frac {-\\langle \\log p_{\\varepsilon }\\rangle }{\\log {\\frac {1}{\\varepsilon }}}}}{\\displaystyle D_{1}=\\lim _{\\varepsilon \\to 0}{\\frac {-\\langle \\log p_{\\varepsilon }\\rangle }{\\log {\\frac {1}{\\varepsilon }}}}}\nCorrelation dimension: D is based on {\\displaystyle M}M as the number of points used to generate a representation of a fractal and gε, the number of pairs of points closer than ε to each other.\n{\\displaystyle D_{2}=\\lim _{M\\to \\infty }\\lim _{\\varepsilon \\to 0}{\\frac {\\log(g_{\\varepsilon }/M^{2})}{\\log \\varepsilon }}}{\\displaystyle D_{2}=\\lim _{M\\to \\infty }\\lim _{\\varepsilon \\to 0}{\\frac {\\log(g_{\\varepsilon }/M^{2})}{\\log \\varepsilon }}}[citation needed]\nGeneralized or Rényi dimensions: The box-counting, information, and correlation dimensions can be seen as special cases of a continuous spectrum of generalized dimensions of order α, defined by:\n{\\displaystyle D_{\\alpha }=\\lim _{\\varepsilon \\to 0}{\\frac {{\\frac {1}{\\alpha -1}}\\log(\\sum _{i}p_{i}^{\\alpha })}{\\log \\varepsilon }}}{\\displaystyle D_{\\alpha }=\\lim _{\\varepsilon \\to 0}{\\frac {{\\frac {1}{\\alpha -1}}\\log(\\sum _{i}p_{i}^{\\alpha })}{\\log \\varepsilon }}}\nHiguchi dimension[31]\n{\\displaystyle D={\\frac {d\\ \\log(L(k))}{d\\ \\log(k)}}}D={\\frac {d\\ \\log(L(k))}{d\\ \\log(k)}}\nLyapunov dimension\nMultifractal dimensions: a special case of Rényi dimensions where scaling behaviour varies in different parts of the pattern.\nUncertainty exponent\nHausdorff dimension: For any subset {\\displaystyle S}S of a metric space {\\displaystyle X}X and {\\displaystyle d\\geq 0}{\\displaystyle d\\geq 0}, the d-dimensional Hausdorff content of S is defined by\n{\\displaystyle C_{H}^{d}(S):=\\inf {\\Bigl \\{}\\sum _{i}r_{i}^{d}:{\\text{ there is a cover of }}S{\\text{ by balls with radii }}r_{i}>0{\\Bigr \\}}.}C_H^d(S):=\\inf\\Bigl\\{\\sum_i r_i^d:\\text{ there is a cover of } S\\text{ by balls with radii }r_i>0\\Bigr\\}.\nThe Hausdorff dimension of S is defined by\n{\\displaystyle \\dim _{\\operatorname {H} }(X):=\\inf\\{d\\geq 0:C_{H}^{d}(X)=0\\}.}\\dim _{{\\operatorname {H}}}(X):=\\inf\\{d\\geq 0:C_{H}^{d}(X)=0\\}.",
      "json_metadata": "{\"tags\":[\"steem\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
dtubesent 0.001 STEEM to @alwaysnew- "DTube Coin Round #1 is live! Visit https://token.d.tube for more information"
2019/09/20 22:04:51
fromdtube
toalwaysnew
amount0.001 STEEM
memoDTube Coin Round #1 is live! Visit https://token.d.tube for more information
Transaction InfoBlock #36598111/Trx ba4c6dde6643aa48653ebd6c50c7e551b3cc70bf
View Raw JSON Data
{
  "trx_id": "ba4c6dde6643aa48653ebd6c50c7e551b3cc70bf",
  "block": 36598111,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-20T22:04:51",
  "op": [
    "transfer",
    {
      "from": "dtube",
      "to": "alwaysnew",
      "amount": "0.001 STEEM",
      "memo": "DTube Coin Round #1 is live! Visit https://token.d.tube for more information"
    }
  ]
}
alwaysnewreplied to @lass3 / pxkam6
2019/09/09 11:30:15
parent authorlass3
parent permlinkpxj7kz
authoralwaysnew
permlinkpxkam6
title
bodywelcome to future lol
json metadata{"tags":["bitcoin"],"app":"steemit/0.1"}
Transaction InfoBlock #36269520/Trx 3785dc9f88a9a76b3a025ea40088f9bd392d9712
View Raw JSON Data
{
  "trx_id": "3785dc9f88a9a76b3a025ea40088f9bd392d9712",
  "block": 36269520,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-09T11:30:15",
  "op": [
    "comment",
    {
      "parent_author": "lass3",
      "parent_permlink": "pxj7kz",
      "author": "alwaysnew",
      "permlink": "pxkam6",
      "title": "",
      "body": "welcome to future lol",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
lass3replied to @alwaysnew / pxj7kz
2019/09/08 21:27:03
parent authoralwaysnew
parent permlinka-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you
authorlass3
permlinkpxj7kz
title
bodyThat is interesting for sure. Ofc someone will find a way to exploit it. If its possible, people will try.
json metadata{"tags":["bitcoin"],"app":"steemit/0.1"}
Transaction InfoBlock #36252720/Trx 433153a247a6d882c50643c1ec89b0d5eebd407a
View Raw JSON Data
{
  "trx_id": "433153a247a6d882c50643c1ec89b0d5eebd407a",
  "block": 36252720,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-08T21:27:03",
  "op": [
    "comment",
    {
      "parent_author": "alwaysnew",
      "parent_permlink": "a-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you",
      "author": "lass3",
      "permlink": "pxj7kz",
      "title": "",
      "body": "That is interesting for sure. Ofc someone will find a way to exploit it. If its possible, people will try.",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2019/09/08 21:14:12
voteralwaysnew
authoralwaysnew
permlinka-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you
weight-10000 (-100.00%)
Transaction InfoBlock #36252464/Trx 2b20686c771848d3a4baec385142e70c2674c68d
View Raw JSON Data
{
  "trx_id": "2b20686c771848d3a4baec385142e70c2674c68d",
  "block": 36252464,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-08T21:14:12",
  "op": [
    "vote",
    {
      "voter": "alwaysnew",
      "author": "alwaysnew",
      "permlink": "a-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you",
      "weight": -10000
    }
  ]
}
2019/09/08 21:12:36
voterhaxxdump
authoralwaysnew
permlinka-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you
weight500 (5.00%)
Transaction InfoBlock #36252432/Trx ed87f599aa065475541ef237f2eec467ced79c9c
View Raw JSON Data
{
  "trx_id": "ed87f599aa065475541ef237f2eec467ced79c9c",
  "block": 36252432,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-08T21:12:36",
  "op": [
    "vote",
    {
      "voter": "haxxdump",
      "author": "alwaysnew",
      "permlink": "a-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you",
      "weight": 500
    }
  ]
}
2019/09/08 21:12:24
parent author
parent permlinkbitcoin
authoralwaysnew
permlinka-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you
titleA new bike that mining cryptocurrencies for everyone who leads them and ensures you a profit according to the distance you traveled
bodyThe UK bicycle manufacturer has manufactured 50 bikes, the world's first electronic bike capable of generating digital coins. The company has developed 50 motorcycles, a bicycle manufacturer in the UK, and is the world's first electronic bike capable of earning cryptocurrency. Although it is, the idea itself is very innovative. ![ggg.png](https://cdn.steemitimages.com/DQmYfTxz2mr3vYfoMcDu2uSdAfhkVZrT38Ho1w8gVNvhUY8/ggg.png) The bike called the Toba will be able to generate LoyalCoin at a rate of approximately £ 20 per 1,000 miles. Once you have enough Toba coins, you can either trade them in Bitcoin, Zen, Litecoin or Digibytes, or exchange them at any store that accepts cryptocurrency. Cyclists will be able to monitor tokens generated using a smartphone app. Each turnover will earn you a Toba wheel, tokens that can be used to buy products from 50 motorcycles at a discount. It's mainly stimulating cycling.  Toba bikes will have their own digital currency which will become one of thousands of coins in the future, and Toba will allow passengers to become an integral part of the growth you know. ![image1.jpg](https://cdn.steemitimages.com/DQmT5sSBqyFc5GaPb8DeibwgNVhueBRhG3Dnx2RQuhHswmi/image1.jpg) There is one issue to think about, people will find ways to trick the game. I can imagine someone disassembling the bike and turning it in a car, for example, or finding a way to make the wheels spin constantly. Someone will inevitably find a way to exploit the system, so it is clear that security measures must be put in place. The Toba will be launched in the UK in September.
json metadata{"tags":["bitcoin"],"image":["https://cdn.steemitimages.com/DQmYfTxz2mr3vYfoMcDu2uSdAfhkVZrT38Ho1w8gVNvhUY8/ggg.png","https://cdn.steemitimages.com/DQmT5sSBqyFc5GaPb8DeibwgNVhueBRhG3Dnx2RQuhHswmi/image1.jpg"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #36252428/Trx b80a0b8d7ac7c70957854b9e0525c3c04aeb666c
View Raw JSON Data
{
  "trx_id": "b80a0b8d7ac7c70957854b9e0525c3c04aeb666c",
  "block": 36252428,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-08T21:12:24",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "bitcoin",
      "author": "alwaysnew",
      "permlink": "a-new-bike-that-mining-cryptocurrencies-for-everyone-who-leads-them-and-ensures-you-a-profit-according-to-the-distance-you",
      "title": "A new bike that mining cryptocurrencies for everyone who leads them and ensures you a profit according to the distance you traveled",
      "body": "The UK bicycle manufacturer has manufactured 50 bikes, the world's first electronic bike capable of generating digital coins.\nThe company has developed 50 motorcycles, a bicycle manufacturer in the UK, and is the world's first electronic bike capable of earning cryptocurrency. Although it is, the idea itself is very innovative.\n\n\n![ggg.png](https://cdn.steemitimages.com/DQmYfTxz2mr3vYfoMcDu2uSdAfhkVZrT38Ho1w8gVNvhUY8/ggg.png)\n\n\nThe bike called the Toba will be able to generate LoyalCoin at a rate of approximately £ 20 per 1,000 miles. Once you have enough Toba coins, you can either trade them in Bitcoin, Zen, Litecoin or Digibytes, or exchange them at any store that accepts cryptocurrency. Cyclists will be able to monitor tokens generated using a smartphone app.\nEach turnover will earn you a Toba wheel, tokens that can be used to buy products from 50 motorcycles at a discount. It's mainly stimulating cycling.\n Toba bikes will have their own digital currency which will become one of thousands of coins in the future, and Toba will allow passengers to become an integral part of the growth you know.\n\n![image1.jpg](https://cdn.steemitimages.com/DQmT5sSBqyFc5GaPb8DeibwgNVhueBRhG3Dnx2RQuhHswmi/image1.jpg)\n\n\n\nThere is one issue to think about, people will find ways to trick the game. I can imagine someone disassembling the bike and turning it in a car, for example, or finding a way to make the wheels spin constantly. Someone will inevitably find a way to exploit the system, so it is clear that security measures must be put in place.\nThe Toba will be launched in the UK in September.",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"image\":[\"https://cdn.steemitimages.com/DQmYfTxz2mr3vYfoMcDu2uSdAfhkVZrT38Ho1w8gVNvhUY8/ggg.png\",\"https://cdn.steemitimages.com/DQmT5sSBqyFc5GaPb8DeibwgNVhueBRhG3Dnx2RQuhHswmi/image1.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2019/09/07 19:58:03
voterpartitura.leo
authoralwaysnew
permlinkfkapptzr3d8
weight10000 (100.00%)
Transaction InfoBlock #36222253/Trx 32126fa4a9b862485b148e0e5cf307f0f2b85b9a
View Raw JSON Data
{
  "trx_id": "32126fa4a9b862485b148e0e5cf307f0f2b85b9a",
  "block": 36222253,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-07T19:58:03",
  "op": [
    "vote",
    {
      "voter": "partitura.leo",
      "author": "alwaysnew",
      "permlink": "fkapptzr3d8",
      "weight": 10000
    }
  ]
}
kiddadyupvoted (100.00%) @alwaysnew / fkapptzr3d8
2019/09/07 16:43:54
voterkiddady
authoralwaysnew
permlinkfkapptzr3d8
weight10000 (100.00%)
Transaction InfoBlock #36218384/Trx 4afee79720690b4fc7bb4c0053426eb41d0dc7be
View Raw JSON Data
{
  "trx_id": "4afee79720690b4fc7bb4c0053426eb41d0dc7be",
  "block": 36218384,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-07T16:43:54",
  "op": [
    "vote",
    {
      "voter": "kiddady",
      "author": "alwaysnew",
      "permlink": "fkapptzr3d8",
      "weight": 10000
    }
  ]
}
alwaysnewupdated options for fkapptzr3d8
2019/09/07 16:39:24
authoralwaysnew
permlinkfkapptzr3d8
max accepted payout1000000.000 SBD
percent steem dollars10000
allow votestrue
allow curation rewardstrue
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
Transaction InfoBlock #36218294/Trx f8a19e24b6660be24011b16a9434575ded44c7f1
View Raw JSON Data
{
  "trx_id": "f8a19e24b6660be24011b16a9434575ded44c7f1",
  "block": 36218294,
  "trx_in_block": 27,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-07T16:39:24",
  "op": [
    "comment_options",
    {
      "author": "alwaysnew",
      "permlink": "fkapptzr3d8",
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "allow_votes": true,
      "allow_curation_rewards": true,
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ]
    }
  ]
}
alwaysnewpublished a new post: fkapptzr3d8
2019/09/07 16:39:24
parent author
parent permlinkdtube
authoralwaysnew
permlinkfkapptzr3d8
titlebitcoin super song
body<center><a href='https://d.tube/#!/v/alwaysnew/fkapptzr3d8'><img src='https://snap1.d.tube/ipfs/QmdBzLHtM7TnoaZhXDRNiaxQxdLSvB9dnJCF8ah8Fb1Nou'></a></center><hr> Bitcoin giveaway rules here ► http://bit.ly/coinrul We're giving away 1 BITCOIN, split between 2 winners: • ½ BTC to a commenter on this video, just tell us who won and why • ½ BTC to a contestant who enters using the alternate entry form http://bit.ly/coinrul Alexander Hamilton and Satoshi Nakamoto engage in a battle rap debate on the merits of centralized and decentralized currencies. What do you think? Let us know in the comments below for a chance to win bitcoin. (Yes, we’re serious.) Watch the behind the scenes to see how this was made ► http://bit.ly/2m0qLJp <hr><a href='https://d.tube/#!/v/alwaysnew/fkapptzr3d8'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmP3zwB9HHSeB9aZAX7L571ePvURE7R3yrU7f4roicjeFq'> ▶️ IPFS</a>
json metadata{"video":{"videoId":"QmP3zwB9HHSeB9aZAX7L571ePvURE7R3yrU7f4roicjeFq","duration":361.581134,"title":"bitcoin super song","description":"Bitcoin giveaway rules here ► http://bit.ly/coinrul\nWe're giving away 1 BITCOIN, split between 2 winners:\n• ½ BTC to a commenter on this video, just tell us who won and why\n• ½ BTC to a contestant who enters using the alternate entry form http://bit.ly/coinrul\n\nAlexander Hamilton and Satoshi Nakamoto engage in a battle rap debate on the merits of centralized and decentralized currencies. What do you think? Let us know in the comments below for a chance to win bitcoin. (Yes, we’re serious.)\n\nWatch the behind the scenes to see how this was made ► \nhttp://bit.ly/2m0qLJp\n\n","filesize":25970308,"ipfs":{"snaphash":"QmdccP6MWNcgFXPfHNmtssELxC8VpVvcqCazvYDRBxawwd","spritehash":"QmVRZKnmZcsLKdxDxGQYrmEHBntWJCfmr96xopkQBBStQg","videohash":"QmP3zwB9HHSeB9aZAX7L571ePvURE7R3yrU7f4roicjeFq","video240hash":"QmSVumdfrnto9wRJtswpa2vZAVto6FdTdC4Hv1DhXQwLHG"},"thumbnailUrl":"https://snap1.d.tube/ipfs/QmdccP6MWNcgFXPfHNmtssELxC8VpVvcqCazvYDRBxawwd","providerName":"IPFS","refs":[]},"tags":["dtube","bitcoin"],"app":"dtube/0.9"}
Transaction InfoBlock #36218294/Trx f8a19e24b6660be24011b16a9434575ded44c7f1
View Raw JSON Data
{
  "trx_id": "f8a19e24b6660be24011b16a9434575ded44c7f1",
  "block": 36218294,
  "trx_in_block": 27,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-07T16:39:24",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "dtube",
      "author": "alwaysnew",
      "permlink": "fkapptzr3d8",
      "title": "bitcoin super song",
      "body": "<center><a href='https://d.tube/#!/v/alwaysnew/fkapptzr3d8'><img src='https://snap1.d.tube/ipfs/QmdBzLHtM7TnoaZhXDRNiaxQxdLSvB9dnJCF8ah8Fb1Nou'></a></center><hr>\n\nBitcoin giveaway rules here ► http://bit.ly/coinrul\nWe're giving away 1 BITCOIN, split between 2 winners:\n• ½ BTC to a commenter on this video, just tell us who won and why\n• ½ BTC to a contestant who enters using the alternate entry form http://bit.ly/coinrul\n\nAlexander Hamilton and Satoshi Nakamoto engage in a battle rap debate on the merits of centralized and decentralized currencies. What do you think? Let us know in the comments below for a chance to win bitcoin. (Yes, we’re serious.)\n\nWatch the behind the scenes to see how this was made ► \nhttp://bit.ly/2m0qLJp\n\n\n\n<hr><a href='https://d.tube/#!/v/alwaysnew/fkapptzr3d8'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmP3zwB9HHSeB9aZAX7L571ePvURE7R3yrU7f4roicjeFq'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"videoId\":\"QmP3zwB9HHSeB9aZAX7L571ePvURE7R3yrU7f4roicjeFq\",\"duration\":361.581134,\"title\":\"bitcoin super song\",\"description\":\"Bitcoin giveaway rules here ► http://bit.ly/coinrul\\nWe're giving away 1 BITCOIN, split between 2 winners:\\n• ½ BTC to a commenter on this video, just tell us who won and why\\n• ½ BTC to a contestant who enters using the alternate entry form http://bit.ly/coinrul\\n\\nAlexander Hamilton and Satoshi Nakamoto engage in a battle rap debate on the merits of centralized and decentralized currencies. What do you think? Let us know in the comments below for a chance to win bitcoin. (Yes, we’re serious.)\\n\\nWatch the behind the scenes to see how this was made ► \\nhttp://bit.ly/2m0qLJp\\n\\n\",\"filesize\":25970308,\"ipfs\":{\"snaphash\":\"QmdccP6MWNcgFXPfHNmtssELxC8VpVvcqCazvYDRBxawwd\",\"spritehash\":\"QmVRZKnmZcsLKdxDxGQYrmEHBntWJCfmr96xopkQBBStQg\",\"videohash\":\"QmP3zwB9HHSeB9aZAX7L571ePvURE7R3yrU7f4roicjeFq\",\"video240hash\":\"QmSVumdfrnto9wRJtswpa2vZAVto6FdTdC4Hv1DhXQwLHG\"},\"thumbnailUrl\":\"https://snap1.d.tube/ipfs/QmdccP6MWNcgFXPfHNmtssELxC8VpVvcqCazvYDRBxawwd\",\"providerName\":\"IPFS\",\"refs\":[]},\"tags\":[\"dtube\",\"bitcoin\"],\"app\":\"dtube/0.9\"}"
    }
  ]
}
steemdelegated 16.411 SP to @alwaysnew
2019/09/06 14:07:24
delegatorsteem
delegateealwaysnew
vesting shares26723.447450 VESTS
Transaction InfoBlock #36186581/Trx ce823276b483e0a2fc8f4e59fb38ff6cbdca011f
View Raw JSON Data
{
  "trx_id": "ce823276b483e0a2fc8f4e59fb38ff6cbdca011f",
  "block": 36186581,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-06T14:07:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "26723.447450 VESTS"
    }
  ]
}
dtubesent 0.001 STEEM to @alwaysnew- "Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube"
2019/09/03 18:03:42
fromdtube
toalwaysnew
amount0.001 STEEM
memoFinal call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube
Transaction InfoBlock #36105376/Trx 81ea974c55bf6529bcb99a5b299cb68ad877a7cc
View Raw JSON Data
{
  "trx_id": "81ea974c55bf6529bcb99a5b299cb68ad877a7cc",
  "block": 36105376,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-03T18:03:42",
  "op": [
    "transfer",
    {
      "from": "dtube",
      "to": "alwaysnew",
      "amount": "0.001 STEEM",
      "memo": "Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube"
    }
  ]
}
steemdelegated 14.586 SP to @alwaysnew
2019/08/24 10:07:03
delegatorsteem
delegateealwaysnew
vesting shares23752.479083 VESTS
Transaction InfoBlock #35829675/Trx 37c1ead133dab9cf30957ac2a018309fb763783e
View Raw JSON Data
{
  "trx_id": "37c1ead133dab9cf30957ac2a018309fb763783e",
  "block": 35829675,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-24T10:07:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "alwaysnew",
      "vesting_shares": "23752.479083 VESTS"
    }
  ]
}
2019/08/19 16:50:42
required auths[]
required posting auths["alwaysnew"]
idfollow
json["follow",{"follower":"alwaysnew","following":"localcoin","what":["blog"]}]
Transaction InfoBlock #35693962/Trx 330224d7a4baee30ad311da366e9454448e96d4f
View Raw JSON Data
{
  "trx_id": "330224d7a4baee30ad311da366e9454448e96d4f",
  "block": 35693962,
  "trx_in_block": 27,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-19T16:50:42",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "alwaysnew"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"alwaysnew\",\"following\":\"localcoin\",\"what\":[\"blog\"]}]"
    }
  ]
}
2019/08/19 16:50:39
parent authorlocalcoin
parent permlinkllc-mining-start-earning-money-now
authoralwaysnew
permlinkpwhtg8
title
bodygood project
json metadata{"tags":["localcoin"],"app":"steemit/0.1"}
Transaction InfoBlock #35693961/Trx a9dc0833470c81e0755098a55e1209bf1790b4b9
View Raw JSON Data
{
  "trx_id": "a9dc0833470c81e0755098a55e1209bf1790b4b9",
  "block": 35693961,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-19T16:50:39",
  "op": [
    "comment",
    {
      "parent_author": "localcoin",
      "parent_permlink": "llc-mining-start-earning-money-now",
      "author": "alwaysnew",
      "permlink": "pwhtg8",
      "title": "",
      "body": "good project",
      "json_metadata": "{\"tags\":[\"localcoin\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2019/08/19 16:50:30
voteralwaysnew
authorlocalcoin
permlinkllc-mining-start-earning-money-now
weight10000 (100.00%)
Transaction InfoBlock #35693958/Trx fc434eb6b7aacc0cc00de9ab0e513e3f6f1f03e6
View Raw JSON Data
{
  "trx_id": "fc434eb6b7aacc0cc00de9ab0e513e3f6f1f03e6",
  "block": 35693958,
  "trx_in_block": 49,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-19T16:50:30",
  "op": [
    "vote",
    {
      "voter": "alwaysnew",
      "author": "localcoin",
      "permlink": "llc-mining-start-earning-money-now",
      "weight": 10000
    }
  ]
}
2019/08/19 16:50:27
voteralwaysnew
authorlocalcoin
permlinkllc-mining-start-earning-money-now
weight10000 (100.00%)
Transaction InfoBlock #35693957/Trx eabb4fc8d6e6a00d1aa747e3af56f3e67d787e01
View Raw JSON Data
{
  "trx_id": "eabb4fc8d6e6a00d1aa747e3af56f3e67d787e01",
  "block": 35693957,
  "trx_in_block": 55,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-19T16:50:27",
  "op": [
    "vote",
    {
      "voter": "alwaysnew",
      "author": "localcoin",
      "permlink": "llc-mining-start-earning-money-now",
      "weight": 10000
    }
  ]
}
2019/07/13 16:38:09
parent authorbarinblog
parent permlinkhow-soon-will-you-start-to-receive-your-profit
authoralwaysnew
permlinkpula7g
title
bodygood project
json metadata{"tags":["profit"],"app":"steemit/0.1"}
Transaction InfoBlock #34631021/Trx db2e3ed173a69e144cdc47cb2dc45ffb44daf78e
View Raw JSON Data
{
  "trx_id": "db2e3ed173a69e144cdc47cb2dc45ffb44daf78e",
  "block": 34631021,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-13T16:38:09",
  "op": [
    "comment",
    {
      "parent_author": "barinblog",
      "parent_permlink": "how-soon-will-you-start-to-receive-your-profit",
      "author": "alwaysnew",
      "permlink": "pula7g",
      "title": "",
      "body": "good project",
      "json_metadata": "{\"tags\":[\"profit\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2019/07/13 16:38:00
required auths[]
required posting auths["alwaysnew"]
idfollow
json["follow",{"follower":"alwaysnew","following":"barinblog","what":["blog"]}]
Transaction InfoBlock #34631018/Trx 54d14431f02b4f2f5c7227cee66b16c1bc4e704b
View Raw JSON Data
{
  "trx_id": "54d14431f02b4f2f5c7227cee66b16c1bc4e704b",
  "block": 34631018,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-13T16:38:00",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "alwaysnew"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"alwaysnew\",\"following\":\"barinblog\",\"what\":[\"blog\"]}]"
    }
  ]
}
2019/07/13 16:38:00
voteralwaysnew
authorbarinblog
permlinkhow-soon-will-you-start-to-receive-your-profit
weight10000 (100.00%)
Transaction InfoBlock #34631018/Trx 9445d03fa6d73c77e2d7d370597e19003c51a824
View Raw JSON Data
{
  "trx_id": "9445d03fa6d73c77e2d7d370597e19003c51a824",
  "block": 34631018,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-13T16:38:00",
  "op": [
    "vote",
    {
      "voter": "alwaysnew",
      "author": "barinblog",
      "permlink": "how-soon-will-you-start-to-receive-your-profit",
      "weight": 10000
    }
  ]
}
fyrstikkenupvoted (10.00%) @alwaysnew / eternode
2019/07/09 13:06:06
voterfyrstikken
authoralwaysnew
permlinketernode
weight1000 (10.00%)
Transaction InfoBlock #34511706/Trx ea87a17cde8c18fe9f4511a314753880644800c2
View Raw JSON Data
{
  "trx_id": "ea87a17cde8c18fe9f4511a314753880644800c2",
  "block": 34511706,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-09T13:06:06",
  "op": [
    "vote",
    {
      "voter": "fyrstikken",
      "author": "alwaysnew",
      "permlink": "eternode",
      "weight": 1000
    }
  ]
}

Account Metadata

POSTING JSON METADATA
profile{"profile_image":"http://www4.0zz0.com/2017/12/22/22/566536215.jpg","cover_image":"http://www4.0zz0.com/2017/12/22/22/566536215.jpg","dtube_pub":"wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo"}
JSON METADATA
profile{"profile_image":"http://www4.0zz0.com/2017/12/22/22/566536215.jpg","cover_image":"http://www4.0zz0.com/2017/12/22/22/566536215.jpg","dtube_pub":"wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo"}
{
  "posting_json_metadata": {
    "profile": {
      "profile_image": "http://www4.0zz0.com/2017/12/22/22/566536215.jpg",
      "cover_image": "http://www4.0zz0.com/2017/12/22/22/566536215.jpg",
      "dtube_pub": "wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo"
    }
  },
  "json_metadata": {
    "profile": {
      "profile_image": "http://www4.0zz0.com/2017/12/22/22/566536215.jpg",
      "cover_image": "http://www4.0zz0.com/2017/12/22/22/566536215.jpg",
      "dtube_pub": "wcyAcKFPJZpUyN33nMySjAqMzfmcfaoZezSLFaJHwjeo"
    }
  }
}

Auth Keys

Owner
Single Signature
Public Keys
STM5hGLySo5rX3oJdLVudTGhot9VVqEiLJbMKYrafuWLE5hrmGKQG1/1
Active
Single Signature
Public Keys
STM68nwjBagTPuxWn3QgkRa93uc4ejAtiyr1ATRY7gKqqcmAyTfxg1/1
Posting
Single Signature
Public Keys
STM6KJznVSC1SehjDSw62ATr5SSE63fLZgiA2cShL1YEnDHNukYjE1/1
App Permissions
Memo
STM8fc7RBGoh9P6FcdrTG12PJoxKrtyjQAEbsuJ8iC13bRBk9A7ny
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5hGLySo5rX3oJdLVudTGhot9VVqEiLJbMKYrafuWLE5hrmGKQG",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM68nwjBagTPuxWn3QgkRa93uc4ejAtiyr1ATRY7gKqqcmAyTfxg",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [
      [
        "dlike.app",
        1
      ],
      [
        "smartsteem",
        1
      ],
      [
        "steemhunt.com",
        1
      ]
    ],
    "key_auths": [
      [
        "STM6KJznVSC1SehjDSw62ATr5SSE63fLZgiA2cShL1YEnDHNukYjE",
        1
      ]
    ]
  },
  "memo": "STM8fc7RBGoh9P6FcdrTG12PJoxKrtyjQAEbsuJ8iC13bRBk9A7ny"
}

Witness Votes

0 / 30
No active witness votes.
[]