Ecoer Logo

@loki-network

25

Private transactions, decentralised communication.

steemit.com/@loki-network
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.019USD
STEEM
0.008STEEM
SBD
0.022SBD
Effective Power
5.007SP
├── Own SP
0.132SP
└── Incoming Deleg
+4.876SP

Detailed Balance

STEEM
balance
0.001STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.007STEEM
STEEM POWER
Own SP
0.132SP
Delegated Out
0.000SP
Delegation In
4.876SP
Effective Power
5.007SP
Reward SP (pending)
0.012SP
SBD
sbd_balance
0.014SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.008SBD
{
  "balance": "0.001 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.007 STEEM",
  "vesting_shares": "214.054691 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7929.605115 VESTS",
  "sbd_balance": "0.014 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.008 SBD",
  "conversions": []
}

Account Info

nameloki-network
id924446
rank414,623
reputation571660238
created2018-04-10T17:25:18
recovery_accountsteem
proxyNone
post_count26
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2019-04-03T23:29:33
last_root_post2019-04-03T23:29:33
last_vote_time2018-04-16T13:08:36
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.001 STEEM
savings_balance0.000 STEEM
sbd_balance0.014 SBD
savings_sbd_balance0.000 SBD
vesting_shares214.054691 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares7929.605115 VESTS
reward_vesting_balance24.357914 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_update2018-04-10T18:33:54
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM7cJeidzu9YSoeRzFM4m4ifiwMz9Ex3XUXia8ca8auz1MnZn78i",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "balance": "0.001 STEEM",
  "can_vote": true,
  "comment_count": 0,
  "created": "2018-04-10T17:25:18",
  "curation_rewards": 0,
  "delegated_vesting_shares": "0.000000 VESTS",
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779073398
  },
  "guest_bloggers": [],
  "id": 924446,
  "json_metadata": "{\"profile\":{\"profile_image\":\"https://yt3.ggpht.com/-2pN4Muif4ck/AAAAAAAAAAI/AAAAAAAAABE/R9xqMkDiBTE/s288-mo-c-c0xffffffff-rj-k-no/photo.jpg\",\"name\":\"Loki Network\",\"about\":\"Private transactions, decentralised communication.\",\"website\":\"https://loki.network/\",\"cover_image\":\"https://yt3.ggpht.com/TX11_sqtQTjzVHwf_k8_xLThTUjmr-d7LpIubY0WvqsQrto5R614STkeO3oKSvoqyc6OuGz0iec=w2120-fcrop64=1,00000000ffffffff-nd-c0xffffffff-rj-k-no\"}}",
  "last_account_recovery": "1970-01-01T00:00:00",
  "last_account_update": "2018-04-10T18:33:54",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_post": "2019-04-03T23:29:33",
  "last_root_post": "2019-04-03T23:29:33",
  "last_vote_time": "2018-04-16T13:08:36",
  "lifetime_vote_count": 0,
  "market_history": [],
  "memo_key": "STM8aQmxhSha2T7zGrgLEcUdiXT1Qcwp7SwSo8jHkjdQZA5tZ5Mxw",
  "mined": false,
  "name": "loki-network",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "other_history": [],
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM8XNZwKp424WE9PavYoM4xNVxGYEgbzyf6ttHUGufzvm6AxvZsy",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "pending_claimed_accounts": 0,
  "post_bandwidth": 0,
  "post_count": 26,
  "post_history": [],
  "posting": {
    "account_auths": [
      [
        "dtube.app",
        1
      ]
    ],
    "key_auths": [
      [
        "STM7RZBhdS6p5Py8poTqcSeqh6mMqWQRaGFBdvCpFKyfZVEfPjaCK",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://yt3.ggpht.com/-2pN4Muif4ck/AAAAAAAAAAI/AAAAAAAAABE/R9xqMkDiBTE/s288-mo-c-c0xffffffff-rj-k-no/photo.jpg\",\"name\":\"Loki Network\",\"about\":\"Private transactions, decentralised communication.\",\"website\":\"https://loki.network/\",\"cover_image\":\"https://yt3.ggpht.com/TX11_sqtQTjzVHwf_k8_xLThTUjmr-d7LpIubY0WvqsQrto5R614STkeO3oKSvoqyc6OuGz0iec=w2120-fcrop64=1,00000000ffffffff-nd-c0xffffffff-rj-k-no\"}}",
  "posting_rewards": 34,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "proxy": "",
  "received_vesting_shares": "7929.605115 VESTS",
  "recovery_account": "steem",
  "reputation": 571660238,
  "reset_account": "null",
  "reward_sbd_balance": "0.008 SBD",
  "reward_steem_balance": "0.007 STEEM",
  "reward_vesting_balance": "24.357914 VESTS",
  "reward_vesting_steem": "0.012 STEEM",
  "savings_balance": "0.000 STEEM",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "sbd_balance": "0.014 SBD",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "2018-04-26T05:12:12",
  "tags_usage": [],
  "to_withdraw": 0,
  "transfer_history": [],
  "vesting_balance": "0.000 STEEM",
  "vesting_shares": "214.054691 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "vote_history": [],
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779073398
  },
  "voting_power": 0,
  "withdraw_routes": 0,
  "withdrawn": 0,
  "witness_votes": [],
  "witnesses_voted_for": 0,
  "rank": 414623
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 4.876 SP to @loki-network
2026/05/18 03:03:18
delegateeloki-network
delegatorsteem
vesting shares7929.605115 VESTS
Transaction InfoBlock #106146793/Trx 3483f56d73ef4c8d44592ac909621465e5a7f059
View Raw JSON Data
{
  "block": 106146793,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "7929.605115 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-18T03:03:18",
  "trx_id": "3483f56d73ef4c8d44592ac909621465e5a7f059",
  "trx_in_block": 2,
  "virtual_op": 0
}
steemdelegated 3.208 SP to @loki-network
2026/05/12 15:10:27
delegateeloki-network
delegatorsteem
vesting shares5217.394710 VESTS
Transaction InfoBlock #105989280/Trx 5ad1561924159f7416e5ba072e4fbf96a1b42adf
View Raw JSON Data
{
  "block": 105989280,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "5217.394710 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-12T15:10:27",
  "trx_id": "5ad1561924159f7416e5ba072e4fbf96a1b42adf",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 4.883 SP to @loki-network
2026/04/26 02:19:51
delegateeloki-network
delegatorsteem
vesting shares7942.120871 VESTS
Transaction InfoBlock #105514367/Trx 6a07ba1959a64c6de342a62321904b30a6402a22
View Raw JSON Data
{
  "block": 105514367,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "7942.120871 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-04-26T02:19:51",
  "trx_id": "6a07ba1959a64c6de342a62321904b30a6402a22",
  "trx_in_block": 28,
  "virtual_op": 0
}
steemdelegated 3.234 SP to @loki-network
2026/01/23 15:17:24
delegateeloki-network
delegatorsteem
vesting shares5258.941529 VESTS
Transaction InfoBlock #102860785/Trx 2ab2b98dea3ae2183149e973b91d055d013ef4a9
View Raw JSON Data
{
  "block": 102860785,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "5258.941529 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-01-23T15:17:24",
  "trx_id": "2ab2b98dea3ae2183149e973b91d055d013ef4a9",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 3.335 SP to @loki-network
2024/12/17 10:31:30
delegateeloki-network
delegatorsteem
vesting shares5423.160726 VESTS
Transaction InfoBlock #91307078/Trx 47b125c00e93dda5c85f371fd1ff9386c208250c
View Raw JSON Data
{
  "block": 91307078,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "5423.160726 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2024-12-17T10:31:30",
  "trx_id": "47b125c00e93dda5c85f371fd1ff9386c208250c",
  "trx_in_block": 3,
  "virtual_op": 0
}
steemdelegated 3.439 SP to @loki-network
2023/11/14 02:13:45
delegateeloki-network
delegatorsteem
vesting shares5592.294258 VESTS
Transaction InfoBlock #79861263/Trx bfd59d06b3cc0ee75d1d5767c4b1fff350282461
View Raw JSON Data
{
  "block": 79861263,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "5592.294258 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-11-14T02:13:45",
  "trx_id": "bfd59d06b3cc0ee75d1d5767c4b1fff350282461",
  "trx_in_block": 3,
  "virtual_op": 0
}
steemdelegated 5.245 SP to @loki-network
2023/09/22 01:07:03
delegateeloki-network
delegatorsteem
vesting shares8529.573044 VESTS
Transaction InfoBlock #78351764/Trx fa0b3749e422435cae508fe0f98d781afafd8421
View Raw JSON Data
{
  "block": 78351764,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "8529.573044 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-09-22T01:07:03",
  "trx_id": "fa0b3749e422435cae508fe0f98d781afafd8421",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 5.381 SP to @loki-network
2022/11/03 14:30:24
delegateeloki-network
delegatorsteem
vesting shares8751.254482 VESTS
Transaction InfoBlock #69116607/Trx a5d94460ed82119792dcbff9fbe6b44cd85611f6
View Raw JSON Data
{
  "block": 69116607,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "8751.254482 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-11-03T14:30:24",
  "trx_id": "a5d94460ed82119792dcbff9fbe6b44cd85611f6",
  "trx_in_block": 7,
  "virtual_op": 0
}
steemdelegated 5.516 SP to @loki-network
2022/01/17 17:48:00
delegateeloki-network
delegatorsteem
vesting shares8971.489618 VESTS
Transaction InfoBlock #60817587/Trx 6274b76cd28dd94bf9e985dd4692ce1417a67d2c
View Raw JSON Data
{
  "block": 60817587,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "8971.489618 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-01-17T17:48:00",
  "trx_id": "6274b76cd28dd94bf9e985dd4692ce1417a67d2c",
  "trx_in_block": 63,
  "virtual_op": 0
}
steemdelegated 5.629 SP to @loki-network
2021/06/14 03:20:30
delegateeloki-network
delegatorsteem
vesting shares9155.556371 VESTS
Transaction InfoBlock #54610738/Trx 5a9624001e52057b0d297bafa6e6c1c6bd1eaeca
View Raw JSON Data
{
  "block": 54610738,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "9155.556371 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-06-14T03:20:30",
  "trx_id": "5a9624001e52057b0d297bafa6e6c1c6bd1eaeca",
  "trx_in_block": 2,
  "virtual_op": 0
}
steemdelegated 5.745 SP to @loki-network
2020/12/11 13:36:12
delegateeloki-network
delegatorsteem
vesting shares9342.978345 VESTS
Transaction InfoBlock #49358103/Trx aa02ed9feea0a3bda4126880134597fab0a75d2c
View Raw JSON Data
{
  "block": 49358103,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "9342.978345 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-11T13:36:12",
  "trx_id": "aa02ed9feea0a3bda4126880134597fab0a75d2c",
  "trx_in_block": 21,
  "virtual_op": 0
}
steemdelegated 1.176 SP to @loki-network
2020/12/06 07:12:36
delegateeloki-network
delegatorsteem
vesting shares1912.543513 VESTS
Transaction InfoBlock #49209644/Trx de7f0fc2338c640d1b0cfea26c4b35d9626b38e9
View Raw JSON Data
{
  "block": 49209644,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "1912.543513 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-06T07:12:36",
  "trx_id": "de7f0fc2338c640d1b0cfea26c4b35d9626b38e9",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 5.749 SP to @loki-network
2020/12/05 17:14:06
delegateeloki-network
delegatorsteem
vesting shares9349.186199 VESTS
Transaction InfoBlock #49193190/Trx 4b3c93d728e45099bfcc74313225ade626249265
View Raw JSON Data
{
  "block": 49193190,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "9349.186199 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-05T17:14:06",
  "trx_id": "4b3c93d728e45099bfcc74313225ade626249265",
  "trx_in_block": 9,
  "virtual_op": 0
}
steemdelegated 1.181 SP to @loki-network
2020/11/02 20:46:03
delegateeloki-network
delegatorsteem
vesting shares1920.017158 VESTS
Transaction InfoBlock #48263841/Trx 4be0aa62a3988f808258b58e20eb94b24f6ad184
View Raw JSON Data
{
  "block": 48263841,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "1920.017158 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-11-02T20:46:03",
  "trx_id": "4be0aa62a3988f808258b58e20eb94b24f6ad184",
  "trx_in_block": 2,
  "virtual_op": 0
}
steemdelegated 5.873 SP to @loki-network
2020/05/09 08:12:42
delegateeloki-network
delegatorsteem
vesting shares9551.991558 VESTS
Transaction InfoBlock #43219930/Trx cf1a1a8a58b7122f1cd8963a2c381b7731da3fd1
View Raw JSON Data
{
  "block": 43219930,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "9551.991558 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-09T08:12:42",
  "trx_id": "cf1a1a8a58b7122f1cd8963a2c381b7731da3fd1",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 1.201 SP to @loki-network
2020/05/08 12:11:12
delegateeloki-network
delegatorsteem
vesting shares1953.311140 VESTS
Transaction InfoBlock #43196468/Trx 22566273e6eccc04ecc21abda489fdb9db6bab0d
View Raw JSON Data
{
  "block": 43196468,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "1953.311140 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-08T12:11:12",
  "trx_id": "22566273e6eccc04ecc21abda489fdb9db6bab0d",
  "trx_in_block": 0,
  "virtual_op": 0
}
dtubesent 0.001 STEEM to @loki-network- "Time is running out, claim your DTube account now before anyone else can! Login at https://d.tube"
2019/08/22 17:38:06
amount0.001 STEEM
fromdtube
memoTime is running out, claim your DTube account now before anyone else can! Login at https://d.tube
toloki-network
Transaction InfoBlock #35781170/Trx 08c153940cf7bf18036b894d84f2ab1bedb1d60a
View Raw JSON Data
{
  "block": 35781170,
  "op": [
    "transfer",
    {
      "amount": "0.001 STEEM",
      "from": "dtube",
      "memo": "Time is running out, claim your DTube account now before anyone else can! Login at https://d.tube",
      "to": "loki-network"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-08-22T17:38:06",
  "trx_id": "08c153940cf7bf18036b894d84f2ab1bedb1d60a",
  "trx_in_block": 19,
  "virtual_op": 0
}
steemdelegated 5.983 SP to @loki-network
2019/07/04 01:46:18
delegateeloki-network
delegatorsteem
vesting shares9730.133353 VESTS
Transaction InfoBlock #34354241/Trx 0d55f44423eb576b9e372fc15c92044decbafbb7
View Raw JSON Data
{
  "block": 34354241,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "9730.133353 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-07-04T01:46:18",
  "trx_id": "0d55f44423eb576b9e372fc15c92044decbafbb7",
  "trx_in_block": 1,
  "virtual_op": 0
}
2019/04/10 19:30:48
authorsteemitboard
bodyCongratulations @loki-network! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@loki-network/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@loki-network) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=loki-network)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/the-steem-blockchain-survived-its-first-virus-plague"><img src="https://steemitimages.com/64x128/https://steemitimages.com/0x0/![](https://cdn.steemitimages.com/DQmYKnawrtqFCShyVvVs4QS7548eretcMUKQJc3D2f69pb9/image.png)"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/the-steem-blockchain-survived-its-first-virus-plague">The Steem blockchain survived its first virus plague!</a></td></tr></table> ###### [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"]}
parent authorloki-network
parent permlink1m39k4vy
permlinksteemitboard-notify-loki-network-20190410t193047000z
title
Transaction InfoBlock #31931144/Trx a23d580e96d49d1fd454705d6628e467a953e3bb
View Raw JSON Data
{
  "block": 31931144,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @loki-network! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@loki-network/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@loki-network) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=loki-network)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/the-steem-blockchain-survived-its-first-virus-plague\"><img src=\"https://steemitimages.com/64x128/https://steemitimages.com/0x0/![](https://cdn.steemitimages.com/DQmYKnawrtqFCShyVvVs4QS7548eretcMUKQJc3D2f69pb9/image.png)\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/the-steem-blockchain-survived-its-first-virus-plague\">The Steem blockchain survived its first virus plague!</a></td></tr></table>\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\"]}",
      "parent_author": "loki-network",
      "parent_permlink": "1m39k4vy",
      "permlink": "steemitboard-notify-loki-network-20190410t193047000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-10T19:30:48",
  "trx_id": "a23d580e96d49d1fd454705d6628e467a953e3bb",
  "trx_in_block": 5,
  "virtual_op": 0
}
loki-networkupdated options for 1m39k4vy
2019/04/03 23:29:33
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlink1m39k4vy
Transaction InfoBlock #31734808/Trx d31bedd65f4072591717e2a01fa6df8a31160fa0
View Raw JSON Data
{
  "block": 31734808,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "1m39k4vy"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T23:29:33",
  "trx_id": "d31bedd65f4072591717e2a01fa6df8a31160fa0",
  "trx_in_block": 34,
  "virtual_op": 0
}
loki-networkpublished a new post: 1m39k4vy
2019/04/03 23:29:33
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/1m39k4vy'><img src='https://ipfs.io/ipfs/QmYiw9TeBC1MTgv39WePdJUet9EEaEnzZhnaFrJrqtdiwe'></a></center><hr> Loki Docs: https://loki-project.github.io/loki-docs/ Service Node as a Service Guide: https://loki-project.github.io/loki-docs/ServiceNodes/RunServiceNodeAsService/ Loki Service Node Video Tutorial: https://www.youtube.com/watch?v=6uiRD1847UY&t Service Node written Guide: https://loki-project.github.io/loki-docs/ServiceNodes/SNFullGuide/ <hr><a href='https://d.tube/#!/v/loki-network/1m39k4vy'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmSVmiFqaqGANenEv9BjsuQqNxo6JgWSFVw838Uwury5tm'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"What Can A Service Node Do_ QnA","snaphash":"QmXy7fkw929PzyriW3eW2FMcVMFUywPug56yK8GCQimiWg","author":"loki-network","permlink":"1m39k4vy","duration":1221.160635,"filesize":73445742,"spritehash":"Qmf55ZsqC1s7vRbcze7d3CnLeQodB6JNEAEnppJZ9ML6pJ"},"content":{"videohash":"QmSVmiFqaqGANenEv9BjsuQqNxo6JgWSFVw838Uwury5tm","description":"Loki Docs: https://loki-project.github.io/loki-docs/\nService Node as a Service Guide: https://loki-project.github.io/loki-docs/ServiceNodes/RunServiceNodeAsService/\nLoki Service Node Video Tutorial: https://www.youtube.com/watch?v=6uiRD1847UY&t\nService Node written Guide: https://loki-project.github.io/loki-docs/ServiceNodes/SNFullGuide/","tags":["lokinetwork","loki","servicenode","lokinet"],"video240hash":"QmYJQR4oAP1HsuzYmMWkvpyRZNx3oR3nsYnWDtYzbU4WoF","video480hash":"QmS7eWoBS9DDKBFkGBVkiCSYoK6i7BjJmgzbiuTF4ttnhe"}},"tags":["dtube","lokinetwork","loki","servicenode","lokinet"],"app":"dtube/0.8"}
parent author
parent permlinkdtube
permlink1m39k4vy
titleWhat Can A Service Node Do_ QnA
Transaction InfoBlock #31734808/Trx d31bedd65f4072591717e2a01fa6df8a31160fa0
View Raw JSON Data
{
  "block": 31734808,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/1m39k4vy'><img src='https://ipfs.io/ipfs/QmYiw9TeBC1MTgv39WePdJUet9EEaEnzZhnaFrJrqtdiwe'></a></center><hr>\n\nLoki Docs: https://loki-project.github.io/loki-docs/\nService Node as a Service Guide: https://loki-project.github.io/loki-docs/ServiceNodes/RunServiceNodeAsService/\nLoki Service Node Video Tutorial: https://www.youtube.com/watch?v=6uiRD1847UY&t\nService Node written Guide: https://loki-project.github.io/loki-docs/ServiceNodes/SNFullGuide/\n\n<hr><a href='https://d.tube/#!/v/loki-network/1m39k4vy'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmSVmiFqaqGANenEv9BjsuQqNxo6JgWSFVw838Uwury5tm'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"What Can A Service Node Do_ QnA\",\"snaphash\":\"QmXy7fkw929PzyriW3eW2FMcVMFUywPug56yK8GCQimiWg\",\"author\":\"loki-network\",\"permlink\":\"1m39k4vy\",\"duration\":1221.160635,\"filesize\":73445742,\"spritehash\":\"Qmf55ZsqC1s7vRbcze7d3CnLeQodB6JNEAEnppJZ9ML6pJ\"},\"content\":{\"videohash\":\"QmSVmiFqaqGANenEv9BjsuQqNxo6JgWSFVw838Uwury5tm\",\"description\":\"Loki Docs: https://loki-project.github.io/loki-docs/\\nService Node as a Service Guide: https://loki-project.github.io/loki-docs/ServiceNodes/RunServiceNodeAsService/\\nLoki Service Node Video Tutorial: https://www.youtube.com/watch?v=6uiRD1847UY&t\\nService Node written Guide: https://loki-project.github.io/loki-docs/ServiceNodes/SNFullGuide/\",\"tags\":[\"lokinetwork\",\"loki\",\"servicenode\",\"lokinet\"],\"video240hash\":\"QmYJQR4oAP1HsuzYmMWkvpyRZNx3oR3nsYnWDtYzbU4WoF\",\"video480hash\":\"QmS7eWoBS9DDKBFkGBVkiCSYoK6i7BjJmgzbiuTF4ttnhe\"}},\"tags\":[\"dtube\",\"lokinetwork\",\"loki\",\"servicenode\",\"lokinet\"],\"app\":\"dtube/0.8\"}",
      "parent_author": "",
      "parent_permlink": "dtube",
      "permlink": "1m39k4vy",
      "title": "What Can A Service Node Do_ QnA"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T23:29:33",
  "trx_id": "d31bedd65f4072591717e2a01fa6df8a31160fa0",
  "trx_in_block": 34,
  "virtual_op": 0
}
loki-networkupdated options for fds7rrf9
2019/04/03 23:15:48
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlinkfds7rrf9
Transaction InfoBlock #31734533/Trx e968284b54aebe552747e42ec4d3d9b7d7f5d458
View Raw JSON Data
{
  "block": 31734533,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "fds7rrf9"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T23:15:48",
  "trx_id": "e968284b54aebe552747e42ec4d3d9b7d7f5d458",
  "trx_in_block": 22,
  "virtual_op": 0
}
loki-networkpublished a new post: fds7rrf9
2019/04/03 23:15:48
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/fds7rrf9'><img src='https://ipfs.io/ipfs/Qmc4Pa2XHrsYpBp8sEgZwjCTCPgWb3xFidsKrwzPWgajLt'></a></center><hr> Simon Harman and Johnathan Ross demo Lokinet at the RMIT Blockchain Innovation Hub on 16th Jan 2019. <hr><a href='https://d.tube/#!/v/loki-network/fds7rrf9'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmahTFk8S77pkh5q3t2wgMEeKLoG48fbxxLuwU2SX5Utd6'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"Lokinet Alpha Demo","snaphash":"QmYUt4C9sDSKmQmULkhhfbFtrem8GAsY3PCtWpZjhY9xMV","author":"loki-network","permlink":"fds7rrf9","duration":925.129433,"filesize":118379057,"spritehash":"QmXs6qzSKaA7bHGbLUbeNwC7zzske9dxK5BEWG4hQ5RaeD"},"content":{"videohash":"QmahTFk8S77pkh5q3t2wgMEeKLoG48fbxxLuwU2SX5Utd6","description":"Simon Harman and Johnathan Ross demo Lokinet at the RMIT Blockchain Innovation Hub on 16th Jan 2019.","tags":["lokinet","mixnet","loki","blockchain"],"video240hash":"QmQ1odEfA7RnZvV2CNU3ELCkuCYWVi58CV4wZRQgYT6x1A","video480hash":"QmSBbiY7A4h5pi9WhDUMft7NPhK2c1cZavDzW6DxjTq4i6"}},"tags":["dtube","lokinet","mixnet","loki","blockchain"],"app":"dtube/0.8"}
parent author
parent permlinkdtube
permlinkfds7rrf9
titleLokinet Alpha Demo
Transaction InfoBlock #31734533/Trx e968284b54aebe552747e42ec4d3d9b7d7f5d458
View Raw JSON Data
{
  "block": 31734533,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/fds7rrf9'><img src='https://ipfs.io/ipfs/Qmc4Pa2XHrsYpBp8sEgZwjCTCPgWb3xFidsKrwzPWgajLt'></a></center><hr>\n\nSimon Harman and Johnathan Ross demo Lokinet at the RMIT Blockchain Innovation Hub on 16th Jan 2019.\n\n<hr><a href='https://d.tube/#!/v/loki-network/fds7rrf9'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmahTFk8S77pkh5q3t2wgMEeKLoG48fbxxLuwU2SX5Utd6'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"Lokinet Alpha Demo\",\"snaphash\":\"QmYUt4C9sDSKmQmULkhhfbFtrem8GAsY3PCtWpZjhY9xMV\",\"author\":\"loki-network\",\"permlink\":\"fds7rrf9\",\"duration\":925.129433,\"filesize\":118379057,\"spritehash\":\"QmXs6qzSKaA7bHGbLUbeNwC7zzske9dxK5BEWG4hQ5RaeD\"},\"content\":{\"videohash\":\"QmahTFk8S77pkh5q3t2wgMEeKLoG48fbxxLuwU2SX5Utd6\",\"description\":\"Simon Harman and Johnathan Ross demo Lokinet at the RMIT Blockchain Innovation Hub on 16th Jan 2019.\",\"tags\":[\"lokinet\",\"mixnet\",\"loki\",\"blockchain\"],\"video240hash\":\"QmQ1odEfA7RnZvV2CNU3ELCkuCYWVi58CV4wZRQgYT6x1A\",\"video480hash\":\"QmSBbiY7A4h5pi9WhDUMft7NPhK2c1cZavDzW6DxjTq4i6\"}},\"tags\":[\"dtube\",\"lokinet\",\"mixnet\",\"loki\",\"blockchain\"],\"app\":\"dtube/0.8\"}",
      "parent_author": "",
      "parent_permlink": "dtube",
      "permlink": "fds7rrf9",
      "title": "Lokinet Alpha Demo"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T23:15:48",
  "trx_id": "e968284b54aebe552747e42ec4d3d9b7d7f5d458",
  "trx_in_block": 22,
  "virtual_op": 0
}
loki-networkupdated options for nl9ek2dd
2019/04/03 23:00:12
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlinknl9ek2dd
Transaction InfoBlock #31734221/Trx 798ee35ad0cb2c79a2a63070049d529018267815
View Raw JSON Data
{
  "block": 31734221,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "nl9ek2dd"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T23:00:12",
  "trx_id": "798ee35ad0cb2c79a2a63070049d529018267815",
  "trx_in_block": 53,
  "virtual_op": 0
}
loki-networkpublished a new post: nl9ek2dd
2019/04/03 23:00:12
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/nl9ek2dd'><img src='https://ipfs.io/ipfs/QmRdj2V1r4amjCoA9Seo5V52WjfjmAJNXodDQww94PbAj2'></a></center><hr> <hr><a href='https://d.tube/#!/v/loki-network/nl9ek2dd'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmRJm3moQUBCvkmtdx4MtnnzaCQHeUkGSawr3gE3WPLUj7'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"Dev Done Quick- Lokinet #4","snaphash":"QmZ88hvNmmwEmbGfWmKdSTcAJnJuzfiM4sF8m2WP845CB3","author":"loki-network","permlink":"nl9ek2dd","duration":3215.33678,"filesize":1042402160,"spritehash":""},"content":{"videohash":"QmRJm3moQUBCvkmtdx4MtnnzaCQHeUkGSawr3gE3WPLUj7","description":"","tags":["loki","blockchain","developer","lokinet"]}},"tags":["dtube","loki","blockchain","developer","lokinet"],"app":"dtube/0.8"}
parent author
parent permlinkdtube
permlinknl9ek2dd
titleDev Done Quick- Lokinet #4
Transaction InfoBlock #31734221/Trx 798ee35ad0cb2c79a2a63070049d529018267815
View Raw JSON Data
{
  "block": 31734221,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/nl9ek2dd'><img src='https://ipfs.io/ipfs/QmRdj2V1r4amjCoA9Seo5V52WjfjmAJNXodDQww94PbAj2'></a></center><hr>\n\n\n\n<hr><a href='https://d.tube/#!/v/loki-network/nl9ek2dd'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmRJm3moQUBCvkmtdx4MtnnzaCQHeUkGSawr3gE3WPLUj7'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"Dev Done Quick- Lokinet #4\",\"snaphash\":\"QmZ88hvNmmwEmbGfWmKdSTcAJnJuzfiM4sF8m2WP845CB3\",\"author\":\"loki-network\",\"permlink\":\"nl9ek2dd\",\"duration\":3215.33678,\"filesize\":1042402160,\"spritehash\":\"\"},\"content\":{\"videohash\":\"QmRJm3moQUBCvkmtdx4MtnnzaCQHeUkGSawr3gE3WPLUj7\",\"description\":\"\",\"tags\":[\"loki\",\"blockchain\",\"developer\",\"lokinet\"]}},\"tags\":[\"dtube\",\"loki\",\"blockchain\",\"developer\",\"lokinet\"],\"app\":\"dtube/0.8\"}",
      "parent_author": "",
      "parent_permlink": "dtube",
      "permlink": "nl9ek2dd",
      "title": "Dev Done Quick- Lokinet #4"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T23:00:12",
  "trx_id": "798ee35ad0cb2c79a2a63070049d529018267815",
  "trx_in_block": 53,
  "virtual_op": 0
}
2019/04/03 21:27:54
authorsteemitboard
bodyCongratulations @loki-network! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) : <table><tr><td>https://steemitimages.com/60x70/http://steemitboard.com/@loki-network/posts.png?201904032025</td><td>You published more than 20 posts. Your next target is to reach 30 posts.</td></tr> </table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@loki-network) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=loki-network)_</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</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"]}
parent authorloki-network
parent permlinkt6cxd7li
permlinksteemitboard-notify-loki-network-20190403t212753000z
title
Transaction InfoBlock #31732378/Trx ecc79e6d61f577de27334e2d3ebc24b43f8d92fd
View Raw JSON Data
{
  "block": 31732378,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @loki-network! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td>https://steemitimages.com/60x70/http://steemitboard.com/@loki-network/posts.png?201904032025</td><td>You published more than 20 posts. Your next target is to reach 30 posts.</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@loki-network) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=loki-network)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\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\"]}",
      "parent_author": "loki-network",
      "parent_permlink": "t6cxd7li",
      "permlink": "steemitboard-notify-loki-network-20190403t212753000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T21:27:54",
  "trx_id": "ecc79e6d61f577de27334e2d3ebc24b43f8d92fd",
  "trx_in_block": 5,
  "virtual_op": 0
}
lijojp19upvoted (100.00%) @loki-network / t6cxd7li
2019/04/03 20:58:30
authorloki-network
permlinkt6cxd7li
voterlijojp19
weight10000 (100.00%)
Transaction InfoBlock #31731790/Trx f585f14bf782a94211f0b6af51ddd29edaf847e9
View Raw JSON Data
{
  "block": 31731790,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "t6cxd7li",
      "voter": "lijojp19",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T20:58:30",
  "trx_id": "f585f14bf782a94211f0b6af51ddd29edaf847e9",
  "trx_in_block": 14,
  "virtual_op": 0
}
loki-networkupdated options for t6cxd7li
2019/04/03 20:56:18
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlinkt6cxd7li
Transaction InfoBlock #31731746/Trx 35dca9af43ad22a54e62c9dc9033c46d18c239a7
View Raw JSON Data
{
  "block": 31731746,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "t6cxd7li"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T20:56:18",
  "trx_id": "35dca9af43ad22a54e62c9dc9033c46d18c239a7",
  "trx_in_block": 44,
  "virtual_op": 0
}
loki-networkpublished a new post: t6cxd7li
2019/04/03 20:56:18
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/t6cxd7li'><img src='https://ipfs.io/ipfs/QmNSjPg9CVbKsyJ1Kg1oF7YwqzdvfRtiG6z3zWdmNLEvqa'></a></center><hr> <hr><a href='https://d.tube/#!/v/loki-network/t6cxd7li'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmPq3X2BmsU8B3Dq55xBWq2R9focY151dqUqbYeeXkyeAn'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"Dev Done Quick- Lokinet #3","snaphash":"QmfSeV4rYNabUH3UwhZjAG64RQbRtXjNDgVdKJ9qZ4iByt","author":"loki-network","permlink":"t6cxd7li","duration":506.91483,"filesize":139450747,"spritehash":"QmamvV1Z9XkFVfhhRe43zfDh2bib8gnwxLfWUpMn6Dx6YH"},"content":{"videohash":"QmPq3X2BmsU8B3Dq55xBWq2R9focY151dqUqbYeeXkyeAn","description":"","tags":[""],"video240hash":"QmeEjjiuBJXjnQezK7hmptn8Q8VLRUZhhtGWMU1z9vvSAS","video480hash":"QmTEyKVyLF6jCjFhiLipvB48NRDvVGgbvqCSYavxRFvc8R"}},"tags":["dtube",""],"app":"dtube/0.8"}
parent author
parent permlinkdtube
permlinkt6cxd7li
titleDev Done Quick- Lokinet #3
Transaction InfoBlock #31731746/Trx 35dca9af43ad22a54e62c9dc9033c46d18c239a7
View Raw JSON Data
{
  "block": 31731746,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/t6cxd7li'><img src='https://ipfs.io/ipfs/QmNSjPg9CVbKsyJ1Kg1oF7YwqzdvfRtiG6z3zWdmNLEvqa'></a></center><hr>\n\n\n\n<hr><a href='https://d.tube/#!/v/loki-network/t6cxd7li'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmPq3X2BmsU8B3Dq55xBWq2R9focY151dqUqbYeeXkyeAn'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"Dev Done Quick- Lokinet #3\",\"snaphash\":\"QmfSeV4rYNabUH3UwhZjAG64RQbRtXjNDgVdKJ9qZ4iByt\",\"author\":\"loki-network\",\"permlink\":\"t6cxd7li\",\"duration\":506.91483,\"filesize\":139450747,\"spritehash\":\"QmamvV1Z9XkFVfhhRe43zfDh2bib8gnwxLfWUpMn6Dx6YH\"},\"content\":{\"videohash\":\"QmPq3X2BmsU8B3Dq55xBWq2R9focY151dqUqbYeeXkyeAn\",\"description\":\"\",\"tags\":[\"\"],\"video240hash\":\"QmeEjjiuBJXjnQezK7hmptn8Q8VLRUZhhtGWMU1z9vvSAS\",\"video480hash\":\"QmTEyKVyLF6jCjFhiLipvB48NRDvVGgbvqCSYavxRFvc8R\"}},\"tags\":[\"dtube\",\"\"],\"app\":\"dtube/0.8\"}",
      "parent_author": "",
      "parent_permlink": "dtube",
      "permlink": "t6cxd7li",
      "title": "Dev Done Quick- Lokinet #3"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T20:56:18",
  "trx_id": "35dca9af43ad22a54e62c9dc9033c46d18c239a7",
  "trx_in_block": 44,
  "virtual_op": 0
}
loki-networkupdated options for 83zmpwhm
2019/04/03 20:33:18
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlink83zmpwhm
Transaction InfoBlock #31731286/Trx 0e31273e1ebdc731aecaec86b3e3cc45133789f7
View Raw JSON Data
{
  "block": 31731286,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "83zmpwhm"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T20:33:18",
  "trx_id": "0e31273e1ebdc731aecaec86b3e3cc45133789f7",
  "trx_in_block": 7,
  "virtual_op": 0
}
loki-networkpublished a new post: 83zmpwhm
2019/04/03 20:33:18
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/83zmpwhm'><img src='https://ipfs.io/ipfs/QmeoQcqHKEDrDZjLkWbefcweqT31hMTyrysKovvJiXDy3E'></a></center><hr> DDQ: Hours of Lokinet development in time lapse at 1 fps. <hr><a href='https://d.tube/#!/v/loki-network/83zmpwhm'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmPhs4dpMVGF6NrSQssx2o2VPNXAxY9EJTNi4cuovvL83B'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"Dev Done Quick- Lokinet #2","snaphash":"QmaRKu5rUPV3mCXnnMntqKAK7z2LPs7bnREk7xcbTqYszu","author":"loki-network","permlink":"83zmpwhm","duration":416.055147,"filesize":123888770,"spritehash":"QmcqQcMeVkR5MwBZNwEaZnqKMbSDw2PDdVTZDiEipvNq2u"},"content":{"videohash":"QmPhs4dpMVGF6NrSQssx2o2VPNXAxY9EJTNi4cuovvL83B","description":"DDQ: Hours of Lokinet development in time lapse at 1 fps.\n","tags":["lokinet","mixnet","loki","development"],"video240hash":"QmSEJ1GhGQ7r6uK7Ufg7u94kNvTGhrn1sqWCG9Q5aYKdmh","video480hash":"QmNcb4fJozeHh3mSH9MWTD32YsecucUUqwEe7zucRQRAMa"}},"tags":["dtube","lokinet","mixnet","loki","development"],"app":"dtube/0.8"}
parent author
parent permlinkdtube
permlink83zmpwhm
titleDev Done Quick- Lokinet #2
Transaction InfoBlock #31731286/Trx 0e31273e1ebdc731aecaec86b3e3cc45133789f7
View Raw JSON Data
{
  "block": 31731286,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/83zmpwhm'><img src='https://ipfs.io/ipfs/QmeoQcqHKEDrDZjLkWbefcweqT31hMTyrysKovvJiXDy3E'></a></center><hr>\n\nDDQ: Hours of Lokinet development in time lapse at 1 fps.\n\n\n<hr><a href='https://d.tube/#!/v/loki-network/83zmpwhm'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmPhs4dpMVGF6NrSQssx2o2VPNXAxY9EJTNi4cuovvL83B'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"Dev Done Quick- Lokinet #2\",\"snaphash\":\"QmaRKu5rUPV3mCXnnMntqKAK7z2LPs7bnREk7xcbTqYszu\",\"author\":\"loki-network\",\"permlink\":\"83zmpwhm\",\"duration\":416.055147,\"filesize\":123888770,\"spritehash\":\"QmcqQcMeVkR5MwBZNwEaZnqKMbSDw2PDdVTZDiEipvNq2u\"},\"content\":{\"videohash\":\"QmPhs4dpMVGF6NrSQssx2o2VPNXAxY9EJTNi4cuovvL83B\",\"description\":\"DDQ: Hours of Lokinet development in time lapse at 1 fps.\\n\",\"tags\":[\"lokinet\",\"mixnet\",\"loki\",\"development\"],\"video240hash\":\"QmSEJ1GhGQ7r6uK7Ufg7u94kNvTGhrn1sqWCG9Q5aYKdmh\",\"video480hash\":\"QmNcb4fJozeHh3mSH9MWTD32YsecucUUqwEe7zucRQRAMa\"}},\"tags\":[\"dtube\",\"lokinet\",\"mixnet\",\"loki\",\"development\"],\"app\":\"dtube/0.8\"}",
      "parent_author": "",
      "parent_permlink": "dtube",
      "permlink": "83zmpwhm",
      "title": "Dev Done Quick- Lokinet #2"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T20:33:18",
  "trx_id": "0e31273e1ebdc731aecaec86b3e3cc45133789f7",
  "trx_in_block": 7,
  "virtual_op": 0
}
loki-networkupdated options for 2egbmfjo
2019/04/03 20:10:57
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":1000}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlink2egbmfjo
Transaction InfoBlock #31730839/Trx cf4e3bfb628e0886ec0ab7ba04463e37f3569648
View Raw JSON Data
{
  "block": 31730839,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 1000
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "2egbmfjo"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T20:10:57",
  "trx_id": "cf4e3bfb628e0886ec0ab7ba04463e37f3569648",
  "trx_in_block": 9,
  "virtual_op": 0
}
loki-networkpublished a new post: 2egbmfjo
2019/04/03 20:10:57
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/2egbmfjo'><img src='https://ipfs.io/ipfs/QmQcrrrA7xkuvXTWnT1WRH1awouMrfRGYQnyvGbTLA3PCU'></a></center><hr> DDQ: 5-6 hours of Lokinet development in time lapse at 1 fps. <hr><a href='https://d.tube/#!/v/loki-network/2egbmfjo'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmbNZC6338y7fdwkcvfJtZX82XhG1xXL3gMsEiJ1yUswGw'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"Dev Done Quick- Lokinet #1","snaphash":"QmRBkuowJkUrzDvAMjiEMmtiAfz7ypJtcUygDL9t7DsDxm","author":"loki-network","permlink":"2egbmfjo","duration":896.476009,"filesize":153552741,"spritehash":"QmcnQybvvMgrBe6eyn6Eo188KfPZd7UasLoGqTWH4BCFMy"},"content":{"videohash":"QmbNZC6338y7fdwkcvfJtZX82XhG1xXL3gMsEiJ1yUswGw","description":"DDQ: 5-6 hours of Lokinet development in time lapse at 1 fps.\n","tags":["lokinetloki network","loki","development","mixnet","privacy"],"video240hash":"QmXwSH7AcGnkmWZUCy7h2MvkP9wW4A92CXbomihdfRCJVe","video480hash":"QmdGvju1Sc98kMfuWu4UxfaWDdSY6kxqBUipWtZRQyZbXC"}},"tags":["dtube","lokinetloki network","loki","development","mixnet"],"app":"dtube/0.8"}
parent author
parent permlinkdtube
permlink2egbmfjo
titleDev Done Quick- Lokinet #1
Transaction InfoBlock #31730839/Trx cf4e3bfb628e0886ec0ab7ba04463e37f3569648
View Raw JSON Data
{
  "block": 31730839,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/2egbmfjo'><img src='https://ipfs.io/ipfs/QmQcrrrA7xkuvXTWnT1WRH1awouMrfRGYQnyvGbTLA3PCU'></a></center><hr>\n\nDDQ: 5-6 hours of Lokinet development in time lapse at 1 fps.\n\n\n<hr><a href='https://d.tube/#!/v/loki-network/2egbmfjo'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmbNZC6338y7fdwkcvfJtZX82XhG1xXL3gMsEiJ1yUswGw'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"Dev Done Quick- Lokinet #1\",\"snaphash\":\"QmRBkuowJkUrzDvAMjiEMmtiAfz7ypJtcUygDL9t7DsDxm\",\"author\":\"loki-network\",\"permlink\":\"2egbmfjo\",\"duration\":896.476009,\"filesize\":153552741,\"spritehash\":\"QmcnQybvvMgrBe6eyn6Eo188KfPZd7UasLoGqTWH4BCFMy\"},\"content\":{\"videohash\":\"QmbNZC6338y7fdwkcvfJtZX82XhG1xXL3gMsEiJ1yUswGw\",\"description\":\"DDQ: 5-6 hours of Lokinet development in time lapse at 1 fps.\\n\",\"tags\":[\"lokinetloki network\",\"loki\",\"development\",\"mixnet\",\"privacy\"],\"video240hash\":\"QmXwSH7AcGnkmWZUCy7h2MvkP9wW4A92CXbomihdfRCJVe\",\"video480hash\":\"QmdGvju1Sc98kMfuWu4UxfaWDdSY6kxqBUipWtZRQyZbXC\"}},\"tags\":[\"dtube\",\"lokinetloki network\",\"loki\",\"development\",\"mixnet\"],\"app\":\"dtube/0.8\"}",
      "parent_author": "",
      "parent_permlink": "dtube",
      "permlink": "2egbmfjo",
      "title": "Dev Done Quick- Lokinet #1"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T20:10:57",
  "trx_id": "cf4e3bfb628e0886ec0ab7ba04463e37f3569648",
  "trx_in_block": 9,
  "virtual_op": 0
}
2019/04/03 19:31:54
authorloki-network
permlinkmls-and-federated-messaging
voterfilipino
weight1000 (10.00%)
Transaction InfoBlock #31730058/Trx c393f2c7fe929ab5a76e4651e95b86cba72d0e6b
View Raw JSON Data
{
  "block": 31730058,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "mls-and-federated-messaging",
      "voter": "filipino",
      "weight": 1000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T19:31:54",
  "trx_id": "c393f2c7fe929ab5a76e4651e95b86cba72d0e6b",
  "trx_in_block": 10,
  "virtual_op": 0
}
2019/04/03 18:40:33
authorloki-network
bodyhttps://cdn-images-1.medium.com/max/900/1*N6EvmjMl-QfR9CqMvMXf-g.jpeg Over the last few years we have seen the rapid uptake of encrypted messengers like WhatsApp, Wickr, and Signal, and an increase in the availability of encrypted conversations in Telegram and Facebook Messenger. This adoption has been successful because these companies have been able to deliver a comparable user experience to un-encrypted messengers. Although many Person to Person chats are now using encryption, chat applications have struggled to replicate this in the context of group chats. There are a number of ways Loki Messenger can accomplish encrypted group messaging. Broadly speaking, there are two main ideas that must be considered when designing the Loki Group Messaging architecture: **1. ) Scaling — How intensive is the proposed scheme on the Service Node network and the messaging clients?** **2.) Encryption — How secure is the channel, and what features does the proposed scheme have? What impact does the proposed scheme have on scalability?** **How we approach these two factors will determine the way users interact with the system, and based on our research there are several options available. ** In this article, we use some terms that you may not be familiar with: * Synchronous Messaging: Also known as ‘online’ messaging — where the parties must be online and actively interacting in order to send and receive messages. * Asynchronous Messaging: Also known as ‘offline’ messaging — where the parties do not have to be online in order to send and receive messages. * Client Side Fanout: A message must be sent from the client to a number of other users in the group chat. * Server Side Fanout: A message must be sent to a server, which then sends the message to all participants of the group chat. For messaging with only two participants, Loki Messenger has both an Asynchronous mode using Swarm storage on the Service Node network, and a faster Synchronous mode which allows users to send messages directly to each other via Lokinet. With that explained, let’s move on to the potential schemes: ## Scaling **Full P2P** This scheme is similar to the Tox model, where a central server is never established. In a fully P2P (Peer to Peer) propagation scheme, the members of a group must send messages to all other members of the group. In Tox, this is done by arranging the public keys of the members in the group into a ring, and each message is sent to the two mathematically closest members to the sender’s public key. Those peers should then repeat the process until the message is propagated across the entire group. [1] This protocol could also be extended so that users who were offline for a period of time could request the group chat history from a member in the group. The issue with fully P2P systems is that they can be inefficient and are often unreliable. For example, if I create a group chat with two friends and both of them are offline, there is no way for me to send a message that they will get when they come online since there is no storage server — which is the major disadvantage of Synchronous messaging. Additionally, P2P messengers, including Tox, usually rely on some version of Client Side Fanout. For example, if I am in a large group of 200 people and I want to send a message to the group, the cumulative bandwidth consumption of that message is highly inefficient for client devices — when compared with Server Side Fanout. ## Service Node Storage In this model, any Service Node could be elected as a central server for the group chat. Users could establish a unique code specific to their group chat which would dictate which Service Node was responsible for storing messages. This code would then be given to each new user who wanted to join the chat. The Service Node model is highly scalable since each user only needs to send their message to the Service Node once, before it can be requested by the other participants in the group. However, there are a few issues with this model. Firstly, the redundancy of the message storage is reduced as the group becomes reliant on a single Service Node remaining online. This could be remedied by delegating group messaging to Service Node Swarms, however that would burden the Service Node network as the node would have to manage and store a high volume of messages to provide redundancy for the group. It’s possible this could be combated by requiring payment to the Service Node network, or multi-output payment to the Swarm, when the group is created. ## User Hosted Server In this approach, Loki Messenger would allow the introduction of a simple storage server [2] which a user could host inside Lokinet (practically a SNApp). This server would give the operator a .loki address, and other users could use this address to access the operator’s server. With the addition of Loki Name Service (LNS), this .loki address could become a human readable name like “Protests.loki,” and higher powered servers could allow users to host large chat rooms with a single domain and server.[3] Additionally, through LNS, the operator could add subdomains, for example “paris.Protests.loki”. These subdomains give the ability for one host to create multiple rooms within their single server, all with separate group encryption keys so the host cannot eavesdrop on conversations within rooms. Each subdomain costs the price of a single name registration on LNS, and users would be able to negotiate payment with the server operator if they require a new room. ![0_HgJ0m-X2kyHi0eeO.png](https://cdn.steemitimages.com/DQmNpp8EK2ovcv3s7pPeMjsSshaXPwcaxmXP1v8xG18d4EJ/0_HgJ0m-X2kyHi0eeO.png) This option scales well compared to the other options, since each server operator provisions their own level of service depending on how many users they serve, and there is no additional stress put on the Service Node network to store copies of every message for each member of the group. However, User Hosted Servers also introduce an element of trust — the user must trust the operator to reliably store their messages. Though metadata, the major vector of passive attack when using a central server, is removed, as messages are stored on the server using onion routing (Lokinet). It also opens some much larger questions about how malleable we can make the messaging protocol, and whether opening the protocol restricts the speed of development. [Reflections: The Ecosystem is Moving](https://signal.org/blog/the-ecosystem-is-moving/), by one of the Signal founders, discusses this problem in detail. ## Encryption Now that we have covered some of the challenges with scaling, we should also investigate encryption. **Tox** Tox uses a custom implementation, as described below, which encrypts each message for each participant’s keys.[4] “Groupchats use the NaCl/libsodium cryptography library for all cryptography related operations. All group communication is end-to-end encrypted. Message confidentiality, integrity, and repudiability are guaranteed via authenticated encryption, and perfect forward secrecy is also provided. One of the most important security improvements from the old groupchat implementation is the removal of a message-relay mechanism that uses a group-wide shared key. Instead, connections are 1-to-1 (a complete graph), meaning an outbound message is sent once per peer, and encrypted/decrypted using a key unique to each peer.” This scheme provides perfect forward secrecy (PFS) and deniability, but at the expense of poor scaling, so we should consider this a non-option for the reasons described in the scaling section. In terms of scalability, this solution is similar to using the Signal protocol in pairwise operation. ## TextSecure V2/Sender Keys (Signal, WhatsApp) The “senders keys” method is used by Signal and WhatsApp to encrypt messages for a group (discussion can be found on the Signal blog). This scheme provides a higher level of scalability, PFS and deniability, however it fails under post compromise security (PCS). This means If sender keys are stolen or leaked, they can be used to impersonate or read all future group messages. To remedy this, a new sender key message can be broadcast and users can re-establish a secure group, but because these messages must be encrypted and sent to each user individually, this scales poorly. Additionally, users who leave the group force renegotiation of shared keys. The “senders keys” method tends to work best in smaller groups of less than 50. Once the group grows sufficiently, the additional bandwidth overhead of adding new users, departing users, and ordering messages degrades in production applications like Signal.[5] It is also questionable if groups larger than 50–100 members actually require full PFS, because as the group size grows, fewer users verify the identity of added members out of band, and messages can be being leaked by inserting a new member or compromising existing ones. The ‘senders keys’ scheme is the most easily accessible in the context of Loki Messenger, since it is based on the Signal application. It is also a well tested and implemented protocol with known security properties. ## MLS With Tree-Based Diffie Hellman Message Layer Security (MLS) is proposed as a new interoperable standard for encrypted messaging on the internet, similar to TLS — except MLS specifically focuses on secure group messaging. MLS aims to provide both PFS, Deniable authentication, and PCS inside a group environment while still maintaining a high level of scalability. The idea behind MLS is to use a tree-based Diffie Hellman in a group context. Quoting from “On Ends-to-Ends Encryption: Asynchronous Group Messaging with Strong Security Guarantees,” [6] By using the treeKEM method, MLS provides much better scalability (shown below) when creating groups and dealing with members who leave groups. It also provides PCS, which the ‘senders keys’ scheme does not. The full specification for MLS is still being discussed and iterated on by an IETF working group.[7] There are some reference implementations, but as of yet no working end to end encrypted application that has deployed MLS. ![0_OTHkayVSvB2DoO6K.png](https://cdn.steemitimages.com/DQmYgG9qDvHKXaX7Kk6DbyzYRijfxAvh4UEfzdqdPzh3x9r/0_OTHkayVSvB2DoO6K.png) https://eprint.iacr.org/2017/666.pdf “our solution” here is in reference to Tree-based DH using Asynchronous ratchet trees MLS is a promising protocol, however since it is in the draft stages of development at the IETF, it may be unwise to begin work on implementation until the protocol stabilises. Additionally, MLS is still working through some open problems — namely that MLS requires messages to maintain strict ordering, which can be difficult to achieve when in large groups with many clients. MLS is also trying to address state corruption attacks that could deny service to members in the group, which could be performed by a malicious group member. ## Conclusion We’re still exploring the best way to go about group messaging in Loki Messenger, however it seems likely that our first group messaging scheme will involve a user hosted server that utilises the existing ‘senders keys’ encryption scheme to attain it’s security. We will continue to assess MLS as it becomes a more complete specification, with the hopes of eventually providing an open-source implementation in Loki Messenger. If you have any thoughts or questions to add to this discussion, join us on the Discord. ## References [1] “The TokTok Project — Protocol.” https://toktok.ltd/spec.html#group. Accessed 6 Mar. 2019. [2] “GitHub — loki-project/loki-storage-server: Storage server for Loki ….” https://github.com/loki-project/loki-storage-server. Accessed 6 Mar. 2019. [3] “Loki Name Service · Issue #342 · loki-project/loki · GitHub.” 22 Nov. 2018, https://github.com/loki-project/loki/issues/342. Accessed 27 Mar. 2019. [4] “The TokTok Project — Protocol.” https://toktok.ltd/spec.html. Accessed 8 Mar. 2019. [5] “After leaving group user is still able to read new messages · Issue ….” 16 Oct. 2017, https://github.com/signalapp/Signal-Android/issues/7103. Accessed 26 Mar. 2019. [6] “On Ends-to-Ends Encryption — Cryptology ePrint Archive.” https://eprint.iacr.org/2017/666.pdf. Accessed 12 Mar. 2019. [7] “Messaging Layer Security (mls) — IETF Datatracker.” 7 Nov. 2018, https://datatracker.ietf.org/wg/mls/about/. Accessed 26 Mar. 2019. Originally published at [loki.network](https://loki.network/) on March 29, 2019.
json metadata{"tags":["privacy","loki","groupmessaging","encryption","lokimessenger"],"image":["https://cdn-images-1.medium.com/max/900/1*N6EvmjMl-QfR9CqMvMXf-g.jpeg","https://cdn.steemitimages.com/DQmNpp8EK2ovcv3s7pPeMjsSshaXPwcaxmXP1v8xG18d4EJ/0_HgJ0m-X2kyHi0eeO.png","https://cdn.steemitimages.com/DQmYgG9qDvHKXaX7Kk6DbyzYRijfxAvh4UEfzdqdPzh3x9r/0_OTHkayVSvB2DoO6K.png"],"links":["https://signal.org/blog/the-ecosystem-is-moving/","https://eprint.iacr.org/2017/666.pdf","https://toktok.ltd/spec.html#group","https://github.com/loki-project/loki-storage-server","https://github.com/loki-project/loki/issues/342","https://toktok.ltd/spec.html","https://github.com/signalapp/Signal-Android/issues/7103","https://datatracker.ietf.org/wg/mls/about/","https://loki.network/"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkprivacy
permlinkmls-and-federated-messaging
titleMLS and Federated Messaging
Transaction InfoBlock #31729031/Trx 4d2073ba247d6d2b39a580fd2e04a4fcebc952c2
View Raw JSON Data
{
  "block": 31729031,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "https://cdn-images-1.medium.com/max/900/1*N6EvmjMl-QfR9CqMvMXf-g.jpeg\n\nOver the last few years we have seen the rapid uptake of encrypted messengers like WhatsApp, Wickr, and Signal, and an increase in the availability of encrypted conversations in Telegram and Facebook Messenger. This adoption has been successful because these companies have been able to deliver a comparable user experience to un-encrypted messengers. Although many Person to Person chats are now using encryption, chat applications have struggled to replicate this in the context of group chats.\n\nThere are a number of ways Loki Messenger can accomplish encrypted group messaging. Broadly speaking, there are two main ideas that must be considered when designing the Loki Group Messaging architecture:\n\n**1. ) Scaling — How intensive is the proposed scheme on the Service Node network and the messaging clients?**\n\n**2.) Encryption — How secure is the channel, and what features does the proposed scheme have? What impact does the proposed scheme have on scalability?**\n**How we approach these two factors will determine the way users interact with the system, and based on our research there are several options available. **\n\nIn this article, we use some terms that you may not be familiar with:\n\n* Synchronous Messaging: Also known as ‘online’ messaging — where the parties must be online and actively interacting in order to send and receive messages.\n* Asynchronous Messaging: Also known as ‘offline’ messaging — where the parties do not have to be online in order to send and receive messages.\n* Client Side Fanout: A message must be sent from the client to a number of other users in the group chat.\n* Server Side Fanout: A message must be sent to a server, which then sends the message to all participants of the group chat.\n\nFor messaging with only two participants, Loki Messenger has both an Asynchronous mode using Swarm storage on the Service Node network, and a faster Synchronous mode which allows users to send messages directly to each other via Lokinet.\n\nWith that explained, let’s move on to the potential schemes:\n\n## Scaling\n\n**Full P2P**\n\nThis scheme is similar to the Tox model, where a central server is never established. In a fully P2P (Peer to Peer) propagation scheme, the members of a group must send messages to all other members of the group. In Tox, this is done by arranging the public keys of the members in the group into a ring, and each message is sent to the two mathematically closest members to the sender’s public key. Those peers should then repeat the process until the message is propagated across the entire group. [1] This protocol could also be extended so that users who were offline for a period of time could request the group chat history from a member in the group.\n\nThe issue with fully P2P systems is that they can be inefficient and are often unreliable. For example, if I create a group chat with two friends and both of them are offline, there is no way for me to send a message that they will get when they come online since there is no storage server — which is the major disadvantage of Synchronous messaging. Additionally, P2P messengers, including Tox, usually rely on some version of Client Side Fanout. For example, if I am in a large group of 200 people and I want to send a message to the group, the cumulative bandwidth consumption of that message is highly inefficient for client devices — when compared with Server Side Fanout.\n\n## Service Node Storage\nIn this model, any Service Node could be elected as a central server for the group chat. Users could establish a unique code specific to their group chat which would dictate which Service Node was responsible for storing messages. This code would then be given to each new user who wanted to join the chat.\n\nThe Service Node model is highly scalable since each user only needs to send their message to the Service Node once, before it can be requested by the other participants in the group.\n\nHowever, there are a few issues with this model. Firstly, the redundancy of the message storage is reduced as the group becomes reliant on a single Service Node remaining online. This could be remedied by delegating group messaging to Service Node Swarms, however that would burden the Service Node network as the node would have to manage and store a high volume of messages to provide redundancy for the group. It’s possible this could be combated by requiring payment to the Service Node network, or multi-output payment to the Swarm, when the group is created.\n\n## User Hosted Server\nIn this approach, Loki Messenger would allow the introduction of a simple storage server [2] which a user could host inside Lokinet (practically a SNApp). This server would give the operator a .loki address, and other users could use this address to access the operator’s server.\n\nWith the addition of Loki Name Service (LNS), this .loki address could become a human readable name like “Protests.loki,” and higher powered servers could allow users to host large chat rooms with a single domain and server.[3] Additionally, through LNS, the operator could add subdomains, for example “paris.Protests.loki”. These subdomains give the ability for one host to create multiple rooms within their single server, all with separate group encryption keys so the host cannot eavesdrop on conversations within rooms. Each subdomain costs the price of a single name registration on LNS, and users would be able to negotiate payment with the server operator if they require a new room.\n\n![0_HgJ0m-X2kyHi0eeO.png](https://cdn.steemitimages.com/DQmNpp8EK2ovcv3s7pPeMjsSshaXPwcaxmXP1v8xG18d4EJ/0_HgJ0m-X2kyHi0eeO.png)\n\nThis option scales well compared to the other options, since each server operator provisions their own level of service depending on how many users they serve, and there is no additional stress put on the Service Node network to store copies of every message for each member of the group. However, User Hosted Servers also introduce an element of trust — the user must trust the operator to reliably store their messages. Though metadata, the major vector of passive attack when using a central server, is removed, as messages are stored on the server using onion routing (Lokinet).\n\nIt also opens some much larger questions about how malleable we can make the messaging protocol, and whether opening the protocol restricts the speed of development. [Reflections: The Ecosystem is Moving](https://signal.org/blog/the-ecosystem-is-moving/), by one of the Signal founders, discusses this problem in detail.\n\n## Encryption\nNow that we have covered some of the challenges with scaling, we should also investigate encryption.\n\n**Tox**\nTox uses a custom implementation, as described below, which encrypts each message for each participant’s keys.[4]\n\n“Groupchats use the NaCl/libsodium cryptography library for all cryptography related operations. All group communication is end-to-end encrypted. Message confidentiality, integrity, and repudiability are guaranteed via authenticated encryption, and perfect forward secrecy is also provided.\n\nOne of the most important security improvements from the old groupchat implementation is the removal of a message-relay mechanism that uses a group-wide shared key. Instead, connections are 1-to-1 (a complete graph), meaning an outbound message is sent once per peer, and encrypted/decrypted using a key unique to each peer.”\n\nThis scheme provides perfect forward secrecy (PFS) and deniability, but at the expense of poor scaling, so we should consider this a non-option for the reasons described in the scaling section. In terms of scalability, this solution is similar to using the Signal protocol in pairwise operation.\n\n## TextSecure V2/Sender Keys (Signal, WhatsApp)\nThe “senders keys” method is used by Signal and WhatsApp to encrypt messages for a group (discussion can be found on the Signal blog). This scheme provides a higher level of scalability, PFS and deniability, however it fails under post compromise security (PCS). This means If sender keys are stolen or leaked, they can be used to impersonate or read all future group messages. To remedy this, a new sender key message can be broadcast and users can re-establish a secure group, but because these messages must be encrypted and sent to each user individually, this scales poorly. Additionally, users who leave the group force renegotiation of shared keys.\n\nThe “senders keys” method tends to work best in smaller groups of less than 50. Once the group grows sufficiently, the additional bandwidth overhead of adding new users, departing users, and ordering messages degrades in production applications like Signal.[5] It is also questionable if groups larger than 50–100 members actually require full PFS, because as the group size grows, fewer users verify the identity of added members out of band, and messages can be being leaked by inserting a new member or compromising existing ones.\n\nThe ‘senders keys’ scheme is the most easily accessible in the context of Loki Messenger, since it is based on the Signal application. It is also a well tested and implemented protocol with known security properties.\n\n## MLS With Tree-Based Diffie Hellman\nMessage Layer Security (MLS) is proposed as a new interoperable standard for encrypted messaging on the internet, similar to TLS — except MLS specifically focuses on secure group messaging. MLS aims to provide both PFS, Deniable authentication, and PCS inside a group environment while still maintaining a high level of scalability.\n\nThe idea behind MLS is to use a tree-based Diffie Hellman in a group context. Quoting from “On Ends-to-Ends Encryption: Asynchronous Group Messaging with Strong Security Guarantees,” [6]\n\nBy using the treeKEM method, MLS provides much better scalability (shown below) when creating groups and dealing with members who leave groups. It also provides PCS, which the ‘senders keys’ scheme does not. The full specification for MLS is still being discussed and iterated on by an IETF working group.[7] There are some reference implementations, but as of yet no working end to end encrypted application that has deployed MLS.\n\n![0_OTHkayVSvB2DoO6K.png](https://cdn.steemitimages.com/DQmYgG9qDvHKXaX7Kk6DbyzYRijfxAvh4UEfzdqdPzh3x9r/0_OTHkayVSvB2DoO6K.png)\n\nhttps://eprint.iacr.org/2017/666.pdf “our solution” here is in reference to Tree-based DH using Asynchronous ratchet trees\n\nMLS is a promising protocol, however since it is in the draft stages of development at the IETF, it may be unwise to begin work on implementation until the protocol stabilises. Additionally, MLS is still working through some open problems — namely that MLS requires messages to maintain strict ordering, which can be difficult to achieve when in large groups with many clients. MLS is also trying to address state corruption attacks that could deny service to members in the group, which could be performed by a malicious group member.\n\n## Conclusion\nWe’re still exploring the best way to go about group messaging in Loki Messenger, however it seems likely that our first group messaging scheme will involve a user hosted server that utilises the existing ‘senders keys’ encryption scheme to attain it’s security. We will continue to assess MLS as it becomes a more complete specification, with the hopes of eventually providing an open-source implementation in Loki Messenger. \nIf you have any thoughts or questions to add to this discussion, join us on the Discord.\n\n## References\n[1] “The TokTok Project — Protocol.” https://toktok.ltd/spec.html#group. Accessed 6 Mar. 2019.\n\n[2] “GitHub — loki-project/loki-storage-server: Storage server for Loki ….” https://github.com/loki-project/loki-storage-server. Accessed 6 Mar. 2019.\n\n[3] “Loki Name Service · Issue #342 · loki-project/loki · GitHub.” 22 Nov. 2018, https://github.com/loki-project/loki/issues/342. Accessed 27 Mar. 2019.\n\n[4] “The TokTok Project — Protocol.” https://toktok.ltd/spec.html. Accessed 8 Mar. 2019.\n\n[5] “After leaving group user is still able to read new messages · Issue ….” 16 Oct. 2017, https://github.com/signalapp/Signal-Android/issues/7103. Accessed 26 Mar. 2019.\n\n[6] “On Ends-to-Ends Encryption — Cryptology ePrint Archive.” https://eprint.iacr.org/2017/666.pdf. Accessed 12 Mar. 2019.\n\n[7] “Messaging Layer Security (mls) — IETF Datatracker.” 7 Nov. 2018, https://datatracker.ietf.org/wg/mls/about/. Accessed 26 Mar. 2019.\n\nOriginally published at [loki.network](https://loki.network/) on March 29, 2019.",
      "json_metadata": "{\"tags\":[\"privacy\",\"loki\",\"groupmessaging\",\"encryption\",\"lokimessenger\"],\"image\":[\"https://cdn-images-1.medium.com/max/900/1*N6EvmjMl-QfR9CqMvMXf-g.jpeg\",\"https://cdn.steemitimages.com/DQmNpp8EK2ovcv3s7pPeMjsSshaXPwcaxmXP1v8xG18d4EJ/0_HgJ0m-X2kyHi0eeO.png\",\"https://cdn.steemitimages.com/DQmYgG9qDvHKXaX7Kk6DbyzYRijfxAvh4UEfzdqdPzh3x9r/0_OTHkayVSvB2DoO6K.png\"],\"links\":[\"https://signal.org/blog/the-ecosystem-is-moving/\",\"https://eprint.iacr.org/2017/666.pdf\",\"https://toktok.ltd/spec.html#group\",\"https://github.com/loki-project/loki-storage-server\",\"https://github.com/loki-project/loki/issues/342\",\"https://toktok.ltd/spec.html\",\"https://github.com/signalapp/Signal-Android/issues/7103\",\"https://datatracker.ietf.org/wg/mls/about/\",\"https://loki.network/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "privacy",
      "permlink": "mls-and-federated-messaging",
      "title": "MLS and Federated Messaging"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-03T18:40:33",
  "trx_id": "4d2073ba247d6d2b39a580fd2e04a4fcebc952c2",
  "trx_in_block": 21,
  "virtual_op": 0
}
steemdelegated 18.312 SP to @loki-network
2019/04/01 00:57:09
delegateeloki-network
delegatorsteem
vesting shares29782.083953 VESTS
Transaction InfoBlock #31650232/Trx d5e24fdf72667bf5ffbce0c408a1cc677df2a5c9
View Raw JSON Data
{
  "block": 31650232,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "29782.083953 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-04-01T00:57:09",
  "trx_id": "d5e24fdf72667bf5ffbce0c408a1cc677df2a5c9",
  "trx_in_block": 25,
  "virtual_op": 0
}
2019/03/31 21:57:57
authorcheetah
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://loki-project.github.io/loki-docs/ServiceNodes/InfiniteStakingPrimer/
json metadata
parent authorloki-network
parent permlinkinfinite-staking-overview
permlinkcheetah-re-loki-networkinfinite-staking-overview
title
Transaction InfoBlock #31646649/Trx 8af37da6b779a43754571059db5fe6bdaea49b2b
View Raw JSON Data
{
  "block": 31646649,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://loki-project.github.io/loki-docs/ServiceNodes/InfiniteStakingPrimer/",
      "json_metadata": "",
      "parent_author": "loki-network",
      "parent_permlink": "infinite-staking-overview",
      "permlink": "cheetah-re-loki-networkinfinite-staking-overview",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-31T21:57:57",
  "trx_id": "8af37da6b779a43754571059db5fe6bdaea49b2b",
  "trx_in_block": 17,
  "virtual_op": 0
}
2019/03/31 21:57:54
authorloki-network
permlinkinfinite-staking-overview
votercheetah
weight8 (0.08%)
Transaction InfoBlock #31646648/Trx 7dc6dacda65b97269a53ccae87ccf92bf3a61588
View Raw JSON Data
{
  "block": 31646648,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "infinite-staking-overview",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-31T21:57:54",
  "trx_id": "7dc6dacda65b97269a53ccae87ccf92bf3a61588",
  "trx_in_block": 4,
  "virtual_op": 0
}
2019/03/31 21:57:39
authorloki-network
bodyhttps://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png # **Outline For Existing Service Node Participants and Operators** Infinite Staking is an incremental upgrade on the existing staking process that is currently available on the Loki network (currently active in Hardfork 10: Bulletproofs, introduced in Hardfork 9: Service Nodes). With Infinite Staking, Service Nodes do not expire and funds remain locked until a contributor or operator explicitly requests the Service Node to unlock the funds. Since Infinite Staking is an incremental upgrade, most of the steps necessary to register and participate in a Service Node remain the same. A quick overview for the new staking process is summarised for quick grokking. # **Updated Staking Process and Commands** ## **Operators** Operators will still use the following commands when setting up a Service Node. The commands are as follows: * `prepare_registration` in the daemon that is running in --service-node mode * `register_service_node` with the command returned by the daemon. Auto staking is no longer an option. ## **Contributors** Contributors will still use the following command when contributing to a Service Node: * `stake` to contribute to the node. Auto staking is no longer an option. ## **Operators & Contributors (When Service Node Active)** Two new commands have been added to stop your Service Node from staking, and both the contributor and operator can execute these commands: * **(Optional)** `print_locked_stakes` to preview all of the current wallet’s transactions that are locked in a Service Node or blacklisted on the network. * `request_stake_unlock` to request to unlock the stake in 15 days (10800 blocks). # **Unlocking Stakes & Deregistration** Service Nodes will receive block rewards indefinitely until a stake is unlocked or the Service Node becomes deregistered. Unlocking is available via the `request_stake_unlock` in the command line wallet. Once the unlock is requested and the request is included in a block in the blockchain, the Service Node will then expire in 15 days (10800 blocks) and the funds will become unlocked after expiry. In pooled nodes, any contributor that requests the stake to unlock will schedule the Service Node for expiration. All locked stakes in that Service Node will be unlocked in 15 days (10800 blocks). Once the unlock is requested, this process can not be undone or prolonged. Service Node participants will continue receiving rewards until expiration. Under the new system, deregistrations can be issued at any point during the active lifecycle of the Service Node. This is inclusive of the time period during which the Service Node is scheduled for expiry. Getting deregistered removes your Service Node from the network and your stakes are placed into a list of blacklisted transactions. Blacklisted transactions are locked and unspendable for 30 days (21600 blocks) from the block in which the Service Node was deregistered. Receiving a deregistration after participants have already requested the stake to unlock overrides the 15 day (10800 blocks) unlock time, and resets the unlock time to 30 days (21600 blocks). # **Minimum Contribution Rules** Infinite Staking introduces new limitations on the number of transactions that can be contributed to a Service Node, changing the minimum contribution rules for participating in the Service Node. Service Nodes accept at most 4 contributions, meaning the minimum contribution to a Service Node becomes: https://cdn-images-1.medium.com/max/1000/1*JRuMEP-WKezuqMOHKo3GeQ.png In a pooled Service Node with reserved spots, the Minimum Contribution must be either the Reserved Amount or the Contribution determined by the above equation, whichever is larger. https://cdn-images-1.medium.com/max/1000/1*MABvhhCboua_4MOJMXqKCg.png A simple example: if the staking requirement is 24,000 Loki, then if * Operator contributes 50% of the requirement (12,000 Loki) * The next contributor must contribute at least (⅓ * 12,000) Loki i.e. 4000 Loki to become a participant. * If this contributor had reserved a spot for more than 4000 Loki, their Minimum Contribution would be that amount. There are rules in the client software in place to stop users from irreversibly funding a Service Node into an invalid state. # **Staking Changes** Users are no longer allowed to stake on behalf of another participant in the Service Node. All contributions for a participant must come from the same wallet address as the one specified in the Service Node. # **Developer API Changes** **get_service_nodes** Updated/newly added fields: * `requested_unlock_height` – The height at which the stakes will unlock and the Service Node will expire. * `contributors` * `locked_contributions` – An array of each contribution from the contributor that is locked. * `key_image` – A string representation of the locked key image (stake). * `key_image_pub_key` – A string representation of the public key component of a key image. * `amount` – The amount of Loki locked in this contribution. * `get_service_node_blacklisted_key_images` **Retrieve a list of blacklisted transactions from deregistered Service Nodes on the network.** * `blacklist` – An array of each blacklisted transaction from deregistered Service Nodes * `key_image` – A string representation of the blacklisted key image (stake). * `unlock_height` – The height at which the stake can be spent again. Originally published at [loki.network](https://loki.network/) on March 15, 2019.
json metadata{"tags":["infinitestaking","servicenodes","lokinetwork","loki","masternodes"],"image":["https://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png","https://cdn-images-1.medium.com/max/1000/1*JRuMEP-WKezuqMOHKo3GeQ.png","https://cdn-images-1.medium.com/max/1000/1*MABvhhCboua_4MOJMXqKCg.png"],"links":["https://loki.network/"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkinfinitestaking
permlinkinfinite-staking-overview
titleInfinite Staking Overview
Transaction InfoBlock #31646643/Trx 2934dd3725f4631023f386a9e698c29539eab493
View Raw JSON Data
{
  "block": 31646643,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "https://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png\n\n# **Outline For Existing Service Node Participants and Operators**\n\nInfinite Staking is an incremental upgrade on the existing staking process that is currently available on the Loki network (currently active in Hardfork 10: Bulletproofs, introduced in Hardfork 9: Service Nodes). With Infinite Staking, Service Nodes do not expire and funds remain locked until a contributor or operator explicitly requests the Service Node to unlock the funds.\n\nSince Infinite Staking is an incremental upgrade, most of the steps necessary to register and participate in a Service Node remain the same. A quick overview for the new staking process is summarised for quick grokking.\n\n# **Updated Staking Process and Commands**\n\n## **Operators**\n\nOperators will still use the following commands when setting up a Service Node. The commands are as follows:\n\n* `prepare_registration` in the daemon that is running in --service-node mode\n\n* `register_service_node` with the command returned by the daemon. Auto staking is no longer an option.\n\n## **Contributors**\n\nContributors will still use the following command when contributing to a Service Node:\n\n* `stake` to contribute to the node. Auto staking is no longer an option.\n\n## **Operators & Contributors (When Service Node Active)**\n\nTwo new commands have been added to stop your Service Node from staking, and both the contributor and operator can execute these commands:\n\n* **(Optional)** `print_locked_stakes` to preview all of the current wallet’s transactions that are locked in a Service Node or blacklisted on the network.\n\n* `request_stake_unlock` to request to unlock the stake in 15 days (10800 blocks).\n\n# **Unlocking Stakes & Deregistration**\n\nService Nodes will receive block rewards indefinitely until a stake is unlocked or the Service Node becomes deregistered. Unlocking is available via the `request_stake_unlock` in the command line wallet. Once the unlock is requested and the request is included in a block in the blockchain, the Service Node will then expire in 15 days (10800 blocks) and the funds will become unlocked after expiry.\n\nIn pooled nodes, any contributor that requests the stake to unlock will schedule the Service Node for expiration. All locked stakes in that Service Node will be unlocked in 15 days (10800 blocks). Once the unlock is requested, this process can not be undone or prolonged. Service Node participants will continue receiving rewards until expiration.\n\nUnder the new system, deregistrations can be issued at any point during the active lifecycle of the Service Node. This is inclusive of the time period during which the Service Node is scheduled for expiry. Getting deregistered removes your Service Node from the network and your stakes are placed into a list of blacklisted transactions. Blacklisted transactions are locked and unspendable for 30 days (21600 blocks) from the block in which the Service Node was deregistered.\n\nReceiving a deregistration after participants have already requested the stake to unlock overrides the 15 day (10800 blocks) unlock time, and resets the unlock time to 30 days (21600 blocks).\n\n# **Minimum Contribution Rules**\n\nInfinite Staking introduces new limitations on the number of transactions that can be contributed to a Service Node, changing the minimum contribution rules for participating in the Service Node.\n\nService Nodes accept at most 4 contributions, meaning the minimum contribution to a Service Node becomes:\n\nhttps://cdn-images-1.medium.com/max/1000/1*JRuMEP-WKezuqMOHKo3GeQ.png\n\nIn a pooled Service Node with reserved spots, the Minimum Contribution must be either the Reserved Amount or the Contribution determined by the above equation, whichever is larger.\n\nhttps://cdn-images-1.medium.com/max/1000/1*MABvhhCboua_4MOJMXqKCg.png\n\nA simple example: if the staking requirement is 24,000 Loki, then if\n\n* Operator contributes 50% of the requirement (12,000 Loki)\n\n* The next contributor must contribute at least (⅓ * 12,000) Loki i.e. 4000 Loki to become a participant.\n\n* If this contributor had reserved a spot for more than 4000 Loki, their Minimum Contribution would be that amount.\n\nThere are rules in the client software in place to stop users from irreversibly funding a Service Node into an invalid state.\n\n# **Staking Changes**\n\nUsers are no longer allowed to stake on behalf of another participant in the Service Node. All contributions for a participant must come from the same wallet address as the one specified in the Service Node.\n\n# **Developer API Changes**\n\n**get_service_nodes**\n\nUpdated/newly added fields:\n\n* `requested_unlock_height` – The height at which the stakes will unlock and the Service Node will expire.\n* `contributors`\n* `locked_contributions` – An array of each contribution from the contributor that is locked.\n* `key_image` – A string representation of the locked key image (stake).\n* `key_image_pub_key` – A string representation of the public key component of a key image.\n* `amount` – The amount of Loki locked in this contribution.\n* `get_service_node_blacklisted_key_images`\n\n**Retrieve a list of blacklisted transactions from deregistered Service Nodes on the network.**\n\n* `blacklist` – An array of each blacklisted transaction from deregistered Service Nodes\n* `key_image` – A string representation of the blacklisted key image (stake).\n* `unlock_height` – The height at which the stake can be spent again.\n\nOriginally published at [loki.network](https://loki.network/) on March 15, 2019.",
      "json_metadata": "{\"tags\":[\"infinitestaking\",\"servicenodes\",\"lokinetwork\",\"loki\",\"masternodes\"],\"image\":[\"https://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png\",\"https://cdn-images-1.medium.com/max/1000/1*JRuMEP-WKezuqMOHKo3GeQ.png\",\"https://cdn-images-1.medium.com/max/1000/1*MABvhhCboua_4MOJMXqKCg.png\"],\"links\":[\"https://loki.network/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "infinitestaking",
      "permlink": "infinite-staking-overview",
      "title": "Infinite Staking Overview"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-31T21:57:39",
  "trx_id": "2934dd3725f4631023f386a9e698c29539eab493",
  "trx_in_block": 8,
  "virtual_op": 0
}
2019/03/31 21:41:57
authorcheetah
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://medium.com/@LokiNetwork/company-update-december-january-2018-2019-addd8240658f
json metadata
parent authorloki-network
parent permlinkcompany-update-december-january-2018-2019
permlinkcheetah-re-loki-networkcompany-update-december-january-2018-2019
title
Transaction InfoBlock #31646329/Trx 8de6a9f9b721ad4c324f443b132b925a977f66d1
View Raw JSON Data
{
  "block": 31646329,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://medium.com/@LokiNetwork/company-update-december-january-2018-2019-addd8240658f",
      "json_metadata": "",
      "parent_author": "loki-network",
      "parent_permlink": "company-update-december-january-2018-2019",
      "permlink": "cheetah-re-loki-networkcompany-update-december-january-2018-2019",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-31T21:41:57",
  "trx_id": "8de6a9f9b721ad4c324f443b132b925a977f66d1",
  "trx_in_block": 36,
  "virtual_op": 0
}
2019/03/31 21:41:54
authorloki-network
permlinkcompany-update-december-january-2018-2019
votercheetah
weight8 (0.08%)
Transaction InfoBlock #31646328/Trx 13f62f0ba7f7327ab26ca2d27c366fe4f00c74a4
View Raw JSON Data
{
  "block": 31646328,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "company-update-december-january-2018-2019",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-31T21:41:54",
  "trx_id": "13f62f0ba7f7327ab26ca2d27c366fe4f00c74a4",
  "trx_in_block": 20,
  "virtual_op": 0
}
2019/03/31 21:41:42
authorloki-network
bodyhttps://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png **Software Development Services** During the December — January period, we continued to operate with a high level of development capability and efficiency, successfully implementing the Festive Freya Hardfork. While some bugs were discovered after the release, they were minor in nature and were rapidly patched as soon as they were identified. We have improved the staking process for Service Nodes and implemented Bulletproofs, resulting in a reduction of the average transaction size by approximately 90%. Loki Messenger is taking shape while being integrated on the test Service Node swarm functionality. We have been completing milestones on time and are expecting the different Service Node based functions to come together by the end of Q1 or start of Q2. We have made some advancements on returning the Loki Web Wallet to an operating state, which we will aim to release publicly in the coming months. As expected, there were merges from Monero’s code which resulted in Loki core improvements as well as merges from Signal for Loki Messenger. The Gui and Mobile wallet have each received user improvements and have become much more stable in the latest release. For further information on the development of Loki during this period, please refer to the weekly dev updates or view our progress on the Loki Github repository. **Networking Infrastructure & Performance Testing Services.** We have run and maintained critical network infrastructure during this period without any major downtime, other than the short upgrade periods. Testnet Nodes have been running continuously, although we have discovered a number of anomalies while running our tests which we plan to iron out before the next release. We have successfully run services on Lokinet alpha, and were happy to discover third parties integrating their own services on the platform as well. We have released some of the Loki testing tools, such as a dashboard to monitor the overall network and Service Nodes. Since enabling Cloudflare, we have not had any further issues with Loki websites being disrupted or going down. **Marketing Services** During the month of December, we ran an ‘advent calendar’ competition which delivered one of our highest community engagement to date for Loki, coinciding with the Festive Freya hard fork release. During the months of December — January we’ve seen sustained organic growth through most of our social media channels. Reddit has produced the highest increase in organic user interaction, thanks to our constant stream of updates and consistently high quality content. During the Festive Freya competition, the Loki website, Twitter engagement and Reddit received the highest user traffic out of all of the social media platforms we interact with. We have also begun planning for marketing strategies for the year ahead, which will coincide with the next major hard fork and major conferences. We have planned out a possible path to introduce Loki into more Asian markets later in the year. **Media Services** We are now in the later stages of completing a new animation for Lokinet. We are pleased with the progress of the animation and are expecting it to be completed shortly. We overhauled the Loki.network website completely making it easier to use, and we have introduced new features. We have released two blog posts related to SNApps and a blog related the the new encryption laws recently brought out in Australia during this period. There was further publicity and pieces written and published regarding our position on the new bill. We also released content on Youtube related to Service Nodes in the form of a Q & A, and some edited versions of Jeff working on Lokinet. Simon and Kee partook in a number of podcasts and interviews related to Loki; these were well received. We continued to reward community members with personalised community awards. **Documentation Services** Loki Docs have been proactively updated to reflect changes and additions made to Loki services. Loki Docs have now become an essential reference tool for new and current users of all Loki related services. We documented development changes on Github, as well as published weekly development summaries and updates for public perusal. We assisted the LAG with document management and integration procedures. We have also completed multiple exchange application forms, some with over 100 questions related to Loki. In addition, we released a Chinese version of the Loki whitepaper. **PR Services** We have continued to work closely with Wachmans to promote Loki on the global stage. We undertook a number of media opportunities to promote Loki in relation to the controversial Access Bill, recently released in Australia. Wachmans has arranged a speaker role for Loki at Token 2049 conference in Hong Kong during Asia Crypto Week, in March 2019. Loki’s co-founder and project lead, Simon Harman, will present at this conference. We anticipate that we will see more tangible results from the services provided by Wachmans over the next 3–6 months with the launch of our products. **Conference Attendance and Promotional Services** Members of the team attended multiple conferences during the December — January period. Kee and Ryan attended Stanford Blockchain conference in San Francisco to promote Loki and conduct research at the Stanford Centre for Blockchain Research. Multiple members of the team presented a live Alpha demo at RMIT University, Melbourne showing off some of the features of Lokinet, Loki messenger and Snapps. We have booked and paid for a booth at Consensus, in May 2019. Following the conference, we will bring members from the public and key Loki developers from around the world together in New York for a Loki SNAppathon. **Research and Theoretical Development Services** We have continued to stay on the front foot during this period, researching other projects such as Tor, Monero and Signal to be sure we are staying up to date with their development movements and continue to integrate some of the best features from each project into Loki. We have conducted research through Q & A sessions with the community to maintain a transparent and informative position on our development. We have continued to research and build Infinite Staking for Service Nodes to improve the usability for the community members who are running Service Nodes. We have increasingly noticed other projects with lower hashrates being hash attacked, so we conducted further research into Checkpointing and have published a proposal for the improvement on Github. **Data Analytics and Market Research Services** We have collected and monitored data on engagement with Loki’s social media platforms and website since January 2018. In regards to our overall social media growth and presence, we have noticed a consistent increase of interactions and members across the the majority of our social media platforms. With noticeable spikes correlating to major marketing campaigns and developmental implementations. An improved Dashboard was released during this time, which accurately shows the strength of the network. We have begun researching our targeted audiences and possible market share and plan to release the findings of this research in the coming weeks. **Administration and Bookkeeping Services** We completed documentation and negotiated on behalf of LAG to improve liquidity of Loki through exchanges, payment gateways such as Coinpayments and other third party trading gateways. We have safely conducted competitions and safely completed prize payments to puzzle winners from the Festive Freya Advent calendar. Due to the recent loss of Cryptopia, we have increased our efforts in regards to communications during this period with exchanges across the globe, providing them with relevant information. We have also worked with MasterNode websites to correctly share Loki relevant information. The Loki Improvement Proposal related to Checkpointing was also conducted during this period. We have assisted LAG in regards to bookkeeping, storing documentation, organising meetings and communications directly related to the LAG’s operational requirements. Originally published at [loki.network](https://loki.network/) on March 5, 2019.
json metadata{"tags":["lokinetwork","blockchain","masternodes","loki","lagfoundation"],"image":["https://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png"],"links":["https://loki.network/"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinklokinetwork
permlinkcompany-update-december-january-2018-2019
titleCompany Update: December/January 2018/2019
Transaction InfoBlock #31646324/Trx a3c53c5d665d318ea2217ad12e514857651218ad
View Raw JSON Data
{
  "block": 31646324,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "https://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png\n**Software Development Services**\n\nDuring the December — January period, we continued to operate with a high level of development capability and efficiency, successfully implementing the Festive Freya Hardfork. While some bugs were discovered after the release, they were minor in nature and were rapidly patched as soon as they were identified. We have improved the staking process for Service Nodes and implemented Bulletproofs, resulting in a reduction of the average transaction size by approximately 90%. Loki Messenger is taking shape while being integrated on the test Service Node swarm functionality. We have been completing milestones on time and are expecting the different Service Node based functions to come together by the end of Q1 or start of Q2. We have made some advancements on returning the Loki Web Wallet to an operating state, which we will aim to release publicly in the coming months. As expected, there were merges from Monero’s code which resulted in Loki core improvements as well as merges from Signal for Loki Messenger. The Gui and Mobile wallet have each received user improvements and have become much more stable in the latest release. For further information on the development of Loki during this period, please refer to the weekly dev updates or view our progress on the Loki Github repository.\n\n**Networking Infrastructure & Performance Testing Services.**\n\nWe have run and maintained critical network infrastructure during this period without any major downtime, other than the short upgrade periods. Testnet Nodes have been running continuously, although we have discovered a number of anomalies while running our tests which we plan to iron out before the next release. We have successfully run services on Lokinet alpha, and were happy to discover third parties integrating their own services on the platform as well. We have released some of the Loki testing tools, such as a dashboard to monitor the overall network and Service Nodes. Since enabling Cloudflare, we have not had any further issues with Loki websites being disrupted or going down.\n\n**Marketing Services**\n\nDuring the month of December, we ran an ‘advent calendar’ competition which delivered one of our highest community engagement to date for Loki, coinciding with the Festive Freya hard fork release. During the months of December — January we’ve seen sustained organic growth through most of our social media channels. Reddit has produced the highest increase in organic user interaction, thanks to our constant stream of updates and consistently high quality content. During the Festive Freya competition, the Loki website, Twitter engagement and Reddit received the highest user traffic out of all of the social media platforms we interact with. We have also begun planning for marketing strategies for the year ahead, which will coincide with the next major hard fork and major conferences. We have planned out a possible path to introduce Loki into more Asian markets later in the year.\n\n**Media Services**\n\nWe are now in the later stages of completing a new animation for Lokinet. We are pleased with the progress of the animation and are expecting it to be completed shortly. We overhauled the Loki.network website completely making it easier to use, and we have introduced new features. We have released two blog posts related to SNApps and a blog related the the new encryption laws recently brought out in Australia during this period. There was further publicity and pieces written and published regarding our position on the new bill. We also released content on Youtube related to Service Nodes in the form of a Q & A, and some edited versions of Jeff working on Lokinet. Simon and Kee partook in a number of podcasts and interviews related to Loki; these were well received. We continued to reward community members with personalised community awards.\n\n**Documentation Services**\n\nLoki Docs have been proactively updated to reflect changes and additions made to Loki services. Loki Docs have now become an essential reference tool for new and current users of all Loki related services. We documented development changes on Github, as well as published weekly development summaries and updates for public perusal. We assisted the LAG with document management and integration procedures. We have also completed multiple exchange application forms, some with over 100 questions related to Loki. In addition, we released a Chinese version of the Loki whitepaper.\n\n**PR Services**\n\nWe have continued to work closely with Wachmans to promote Loki on the global stage. We undertook a number of media opportunities to promote Loki in relation to the controversial Access Bill, recently released in Australia. Wachmans has arranged a speaker role for Loki at Token 2049 conference in Hong Kong during Asia Crypto Week, in March 2019. Loki’s co-founder and project lead, Simon Harman, will present at this conference. We anticipate that we will see more tangible results from the services provided by Wachmans over the next 3–6 months with the launch of our products.\n\n**Conference Attendance and Promotional Services**\n\nMembers of the team attended multiple conferences during the December — January period. Kee and Ryan attended Stanford Blockchain conference in San Francisco to promote Loki and conduct research at the Stanford Centre for Blockchain Research. Multiple members of the team presented a live Alpha demo at RMIT University, Melbourne showing off some of the features of Lokinet, Loki messenger and Snapps. We have booked and paid for a booth at Consensus, in May 2019. Following the conference, we will bring members from the public and key Loki developers from around the world together in New York for a Loki SNAppathon.\n\n**Research and Theoretical Development Services**\n\nWe have continued to stay on the front foot during this period, researching other projects such as Tor, Monero and Signal to be sure we are staying up to date with their development movements and continue to integrate some of the best features from each project into Loki. We have conducted research through Q & A sessions with the community to maintain a transparent and informative position on our development. We have continued to research and build Infinite Staking for Service Nodes to improve the usability for the community members who are running Service Nodes. We have increasingly noticed other projects with lower hashrates being hash attacked, so we conducted further research into Checkpointing and have published a proposal for the improvement on Github.\n\n**Data Analytics and Market Research Services**\n\nWe have collected and monitored data on engagement with Loki’s social media platforms and website since January 2018. In regards to our overall social media growth and presence, we have noticed a consistent increase of interactions and members across the the majority of our social media platforms. With noticeable spikes correlating to major marketing campaigns and developmental implementations. An improved Dashboard was released during this time, which accurately shows the strength of the network. We have begun researching our targeted audiences and possible market share and plan to release the findings of this research in the coming weeks.\n\n**Administration and Bookkeeping Services**\n\nWe completed documentation and negotiated on behalf of LAG to improve liquidity of Loki through exchanges, payment gateways such as Coinpayments and other third party trading gateways. We have safely conducted competitions and safely completed prize payments to puzzle winners from the Festive Freya Advent calendar. Due to the recent loss of Cryptopia, we have increased our efforts in regards to communications during this period with exchanges across the globe, providing them with relevant information. We have also worked with MasterNode websites to correctly share Loki relevant information. The Loki Improvement Proposal related to Checkpointing was also conducted during this period. We have assisted LAG in regards to bookkeeping, storing documentation, organising meetings and communications directly related to the LAG’s operational requirements.\n\nOriginally published at [loki.network](https://loki.network/) on March 5, 2019.",
      "json_metadata": "{\"tags\":[\"lokinetwork\",\"blockchain\",\"masternodes\",\"loki\",\"lagfoundation\"],\"image\":[\"https://cdn-images-1.medium.com/max/1000/1*Kk1sC7bJozCnfpTkLhMD2g.png\"],\"links\":[\"https://loki.network/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "lokinetwork",
      "permlink": "company-update-december-january-2018-2019",
      "title": "Company Update: December/January 2018/2019"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-31T21:41:42",
  "trx_id": "a3c53c5d665d318ea2217ad12e514857651218ad",
  "trx_in_block": 5,
  "virtual_op": 0
}
steemdelegated 6.049 SP to @loki-network
2018/12/27 20:51:39
delegateeloki-network
delegatorsteem
vesting shares9838.407648 VESTS
Transaction InfoBlock #28940284/Trx 4e6c15e5e6d7b7c7a764bff23ffacbc1cebbde01
View Raw JSON Data
{
  "block": 28940284,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "9838.407648 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-12-27T20:51:39",
  "trx_id": "4e6c15e5e6d7b7c7a764bff23ffacbc1cebbde01",
  "trx_in_block": 44,
  "virtual_op": 0
}
steemdelegated 18.429 SP to @loki-network
2018/12/10 17:03:54
delegateeloki-network
delegatorsteem
vesting shares29972.076363 VESTS
Transaction InfoBlock #28446437/Trx 9556df5e0d9d15faee32347190cbcb576e4ed12f
View Raw JSON Data
{
  "block": 28446437,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "29972.076363 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-12-10T17:03:54",
  "trx_id": "9556df5e0d9d15faee32347190cbcb576e4ed12f",
  "trx_in_block": 11,
  "virtual_op": 0
}
2018/09/27 20:00:18
authorloki-network
permlinkloki-service-nodes-brief-functionality-overview
voterthetroublenotes
weight200 (2.00%)
Transaction InfoBlock #26320173/Trx b3e7cf729a127ea202a8feffe0bc46cf7e49bf6e
View Raw JSON Data
{
  "block": 26320173,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "loki-service-nodes-brief-functionality-overview",
      "voter": "thetroublenotes",
      "weight": 200
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-27T20:00:18",
  "trx_id": "b3e7cf729a127ea202a8feffe0bc46cf7e49bf6e",
  "trx_in_block": 8,
  "virtual_op": 0
}
2018/09/27 19:38:30
authorcheetah
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://loki.network/wp-content/uploads/2018/08/LokiWhitepaperV3_1.pdf
json metadata
parent authorloki-network
parent permlinkloki-service-nodes-brief-functionality-overview
permlinkcheetah-re-loki-networkloki-service-nodes-brief-functionality-overview
title
Transaction InfoBlock #26319737/Trx 63ea1470cb8d495459b4b4869684ce8236a61e3a
View Raw JSON Data
{
  "block": 26319737,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://loki.network/wp-content/uploads/2018/08/LokiWhitepaperV3_1.pdf",
      "json_metadata": "",
      "parent_author": "loki-network",
      "parent_permlink": "loki-service-nodes-brief-functionality-overview",
      "permlink": "cheetah-re-loki-networkloki-service-nodes-brief-functionality-overview",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-27T19:38:30",
  "trx_id": "63ea1470cb8d495459b4b4869684ce8236a61e3a",
  "trx_in_block": 4,
  "virtual_op": 0
}
2018/09/27 19:38:27
authorloki-network
permlinkloki-service-nodes-brief-functionality-overview
votercheetah
weight8 (0.08%)
Transaction InfoBlock #26319736/Trx a5ab7b826184e4c09c35fedbd2ddb38f8d4a97aa
View Raw JSON Data
{
  "block": 26319736,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "loki-service-nodes-brief-functionality-overview",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-27T19:38:27",
  "trx_id": "a5ab7b826184e4c09c35fedbd2ddb38f8d4a97aa",
  "trx_in_block": 1,
  "virtual_op": 0
}
2018/09/27 19:38:18
authorloki-network
bodyAs Loki is the first Monero fork (and CryptoNote coin, by extension) to have an active implementation of Masternodes, we are staggering releases and adding features as we go. This is new territory and each change we make to the the Monero codebase must be extensively tested before release. **What Loki Service Nodes do in the short term?** (Right now) As part of the 1.0.0 release, Loki Masternodes (called Service Nodes) will have minimum functionality; they will store a full copy of the blockchain, and every hour they will publish an uptime proof, which is essentially a ping to the network letting the network know that they are still live. Nodes that have not submitted an uptime proof in 2 hours will be deregistered by voting quorums. Voting quorums are randomly selected sets of 10 nodes which vote on the state of the network every block. Although the first implementation of Masternodes on a Cryptonote coin is a large move forward in the Masternode world, the major advantages that Service Nodes provide during this beginning stage will be greater privacy when transacting. However, Loki Service Nodes have larger plans ahead, and release 1.0.0 represents only the foundation. **In the Medium Term** (3-6 Months) In the medium term we are working towards making Service Nodes useful to the end user. This includes a couple of essential features: Every Service Node will now be a remote node that serves the blockchain to users. Every Service Node can now run tests and collect data on other Service Node performance; they can assess blockchain storage, bandwidth statistics, and provide message storage for Loki Messenger. Based on these tests, Service Nodes can deregister any underperfoming node if the voting quorum reaches consensus. Lokinet will be deployed on Service Nodes, along with the Loki Message server. Adding these features to Service Nodes allows us to deploy our first end-user Loki Service called Loki Messenger. Loki Messenger (based on the Signal protocol) allows users to communicate more privately than ever through the first market-based Sybil resistant mixnet network, Lokinet. **In the Long term** (6-12 Months) In the long term Loki Service Nodes will need to have high capacity bandwidth connections to provide to the Loki network with routing data. Lokinet will become a fully fledged mixnet providing anonymous access to the internet, and will also have direct integration with browsers, providing an integrated solution for private messaging, internet access and finances . **Want to Know More?** Our [Whitepaper](https://loki.network/whitepaper) details the technicals behind Loki’s network architecture and Service Node functionality, and our Cryptoeconomics paper provides an in-depth analysis on the economics around our Service Nodes.
json metadata{"tags":["functionality","loki","servicenodes","masternodes"],"links":["https://loki.network/whitepaper"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkfunctionality
permlinkloki-service-nodes-brief-functionality-overview
titleLoki Service Nodes: Brief Functionality Overview
Transaction InfoBlock #26319733/Trx 757fda4402146b9c9b8c0b8415517c5c7d87dbd2
View Raw JSON Data
{
  "block": 26319733,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "As Loki is the first Monero fork (and CryptoNote coin, by extension) to have an active implementation of Masternodes, we are staggering releases and adding features as we go. This is new territory and each change we make to the the Monero codebase must be extensively tested before release.\n\n \n\n**What Loki Service Nodes do in the short term?** (Right now)\n\nAs part of the 1.0.0 release, Loki Masternodes (called Service Nodes) will have minimum functionality; they will store a full copy of the blockchain, and every hour they will publish an uptime proof, which is essentially a ping to the network letting the network know that they are still live. Nodes that have not submitted an uptime proof in 2 hours will be deregistered by voting quorums. Voting quorums are randomly selected sets of 10 nodes which vote on the state of the network every block.\n\nAlthough the first implementation of Masternodes on a Cryptonote coin is a large move forward in the Masternode world, the major advantages that Service Nodes provide during this beginning stage will be greater privacy when transacting. However, Loki Service Nodes have larger plans ahead, and release 1.0.0 represents only the foundation.\n\n \n\n**In the Medium Term** (3-6 Months)\n\nIn the medium term we are working towards making Service Nodes useful to the end user. This includes a couple of essential features:\n\nEvery Service Node will now be a remote node that serves the blockchain to users.\nEvery Service Node can now run tests and collect data on other Service Node performance; they can assess blockchain storage, bandwidth statistics, and provide message storage for Loki Messenger.\nBased on these tests, Service Nodes can deregister any underperfoming node if the voting quorum reaches consensus.\nLokinet will be deployed on Service Nodes, along with the Loki Message server.\nAdding these features to Service Nodes allows us to deploy our first end-user Loki Service called Loki Messenger. Loki Messenger (based on the Signal protocol) allows users to communicate more privately than ever through the first market-based Sybil resistant mixnet network, Lokinet.\n\n \n\n**In the Long term** (6-12 Months)\n\nIn the long term Loki Service Nodes will need to have high capacity bandwidth connections to provide to the Loki network with routing data. Lokinet will become a fully fledged mixnet providing anonymous access to the internet, and will also have direct integration with browsers, providing an integrated solution for private messaging, internet access and finances .\n\n \n\n**Want to Know More?**\n\nOur [Whitepaper](https://loki.network/whitepaper) details the technicals behind Loki’s network architecture and Service Node functionality, and our Cryptoeconomics paper provides an in-depth analysis on the economics around our Service Nodes.",
      "json_metadata": "{\"tags\":[\"functionality\",\"loki\",\"servicenodes\",\"masternodes\"],\"links\":[\"https://loki.network/whitepaper\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "functionality",
      "permlink": "loki-service-nodes-brief-functionality-overview",
      "title": "Loki Service Nodes: Brief Functionality Overview"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-27T19:38:18",
  "trx_id": "757fda4402146b9c9b8c0b8415517c5c7d87dbd2",
  "trx_in_block": 8,
  "virtual_op": 0
}
2018/09/03 22:57:24
authorloki-network
permlinkservice-nodes-testnet-announcement
votersensation
weight10000 (100.00%)
Transaction InfoBlock #25648578/Trx 7364aff194bf0d20bf9e34c005519787be6b24e3
View Raw JSON Data
{
  "block": 25648578,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "service-nodes-testnet-announcement",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T22:57:24",
  "trx_id": "7364aff194bf0d20bf9e34c005519787be6b24e3",
  "trx_in_block": 22,
  "virtual_op": 0
}
2018/09/03 20:29:45
authorloki-network
permlinkservice-nodes-testnet-announcement
voteralphabot
weight100 (1.00%)
Transaction InfoBlock #25645625/Trx 81e38738ad18f0c9777bffb7c255b02ae32d78ab
View Raw JSON Data
{
  "block": 25645625,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "service-nodes-testnet-announcement",
      "voter": "alphabot",
      "weight": 100
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T20:29:45",
  "trx_id": "81e38738ad18f0c9777bffb7c255b02ae32d78ab",
  "trx_in_block": 53,
  "virtual_op": 0
}
2018/09/03 20:29:36
authorloki-network
body![1_Kk1sC7bJozCnfpTkLhMD2g.png](https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png) Hey Everyone, The development pace in the Loki office has been consistent and quicker than expected, and I’m happy to announce that we will be launching Service Nodes well ahead of schedule. A huge thank you to our two main Service Node developers, [jcktm](https://github.com/jcktm/) and [Doy-lee](https://github.com/Doy-lee), who have been putting in long hours to get this out. This will mark the first time Proof of Service has been implemented on a CryptoNote coin and we’re really excited to have everyone onboard to test it out. **How will the rollout/update process work?** ![1_r2ncvrAR0dbF2-tY-eF88Q.png](https://cdn.steemitimages.com/DQmNcpDfVjx3MzZc9niDEHhwpxig3P3bj64BC1TsJr2HtAP/1_r2ncvrAR0dbF2-tY-eF88Q.png) Beginning on 09/08/2018 (August 9th) the testnet will be restarted with Service Nodes enabled. The testnet will operate for two weeks in this state. During this period, we will make final changes to the Service Node software, fix bugs as they are reported to us, and add features which will be useful for the final release. Bugs found by community members in Service Node software will be rewarded with bounties at the discretion of the Loki team and depending on severity. On 23/08/2018 (August 23rd) we anticipate the release of the final version of the Service node software, including any bug fixes/changes we found in the Service Node testnet period. This release marks a mandatory upgrade period between 23/08/2018 and 20/09/2018. In this period we will contact exchanges, pools, and miners. All clients will need to update their software. Testnet will continue operation with the new changes, however **on 20/09/2018 (September 20th) mainnet and stagenet will hard fork and Service Nodes will be released** in a production environment. Service Nodes already set up on testnet will **NOT** rollover to mainnet, so when the mainnet forks everyone will have the same opportunity to begin operating a service node using real Loki. **What do Service Nodes do in this update?** As part of the rollout process we need to slowly introduce Service Node functionality. In this upcoming fork, Service Nodes will only have the ability to register and receive rewards. There is no complex testing functionality yet enabled. In this fork Service Nodes will not route data other than propagating blockchain data to their peers. However to be rewarded, Service Nodes that are online automatically transmit pings to the network. If a ping is not submitted each hour a node is assumed to be offline and will be deregistered. More complex functionality is being heavily developed as we speak and will be introduced to Service Nodes over the coming months. However, it is essential that we deploy the base functionality of Service Nodes before we can begin integrating more complex testing and begin routing packets on top of service nodes. Remaining features that will be introduced over the coming months: Blink (Instant Transactions) Lokinet (Packet Routing & SNApps) Loki Messenger (Message Storage) Enforced Remote Nodes (Light Client Improvements) **How can I register a Service Node on testnet?** You will need the alpha software from [here](https://github.com/loki-project/loki/releases), and instructions on how to use it are [here](https://github.com/jcktm/loki/blob/service-node-guide/service_node_guide.md), this also includes a guide on how pooled staking works. This guide assumes you know how the CLI and daemon work. If you don’t, a complete guide on staking is in the works, so sit tight! To test Service Nodes, you will need: 100 testnet Loki A VPS, or highly available home server The Loki CLI wallet, and the Loki Daemon On testnet, the staking requirement will be 100 Loki, so everyone can get in and test. We will distribute funds from the testnet foundation wallet, so just ping one of the admins in the Loki telegram or [discord](https://discord.gg/FkwRPSA) and we will send you some testnet Loki to stake. You can also mine testnet loki by running start_mining <address in lokid. We’ve also shortened the staking duration to just 2 days in the testnet, so you should be able to test restaking over the next couple of weeks to familiarise yourself with the process. This would also be a good time for anyone seeking to pool their staking requirement to test out how that functionality works. So jump on testnet and start testing. **How can I provide feedback or submit bugs?** For general feedback and discussion about the software, you can go to the brand new [#service-node-testing discord channel](https://discord.gg/FkwRPSA). If you spot bugs in the code or add features to it, you should submit an issue or pull request to [GitHub](https://github.com/loki-project/loki). The devs will review the bugand include any necessary fixes in the final release. **What are the requirements for setting up a Service Node on Mainnet?** We have been testing various VPS providers across the course of the last few months and we will be making some recommendations based on positive experiences. In the beginning Service Node operators will have much more choice about where they set up their nodes due to the significantly lower stresses they face. When Loki Messenger and Lokinet are finished, the bandwidth requirements will become more onerous and low performance nodes will have to upgrade hardware and network connections or risk being kicked off the network by automated bandwidth testing systems. When a date for Lokinet is set, we will warn Service Node operators at least 30 days in advance so that they can upgrade their servers. **Where can I go for more information on Service Nodes?** We are currently setting up a webpage to act as a central point for operators to stay updated with all of the latest information. This portal will be updated as we produce documentation on Service Nodes. We want to make setting up a Service Node as clear as possible, and provide in-depth explanations on how the process works, so operators don’t end up making expensive mistakes. We are updating the channels in [discord](https://discord.gg/FkwRPSA) to include a dedicated Service Nodes category, so we can have more in-depth discussions about the software and provide support to those having difficulty. Very exciting times! Let’s get testing, LOKIGANG! Originally published at [loki.network](https://loki.network/service-nodes-testnet-release-date-announced/).
json metadata{"tags":["blockchain","servicenodes","loki","lokinet"],"image":["https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png","https://cdn.steemitimages.com/DQmNcpDfVjx3MzZc9niDEHhwpxig3P3bj64BC1TsJr2HtAP/1_r2ncvrAR0dbF2-tY-eF88Q.png"],"links":["https://github.com/jcktm/","https://github.com/Doy-lee","https://github.com/loki-project/loki/releases","https://github.com/jcktm/loki/blob/service-node-guide/service_node_guide.md","https://discord.gg/FkwRPSA","https://github.com/loki-project/loki","https://loki.network/service-nodes-testnet-release-date-announced/"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkblockchain
permlinkservice-nodes-testnet-announcement
titleService Nodes Testnet Announcement
Transaction InfoBlock #25645622/Trx bd75622712872e69f13400aa8d96151aef1e68ad
View Raw JSON Data
{
  "block": 25645622,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "![1_Kk1sC7bJozCnfpTkLhMD2g.png](https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png)\n\nHey Everyone,\n\nThe development pace in the Loki office has been consistent and quicker than expected, and I’m happy to announce that we will be launching Service Nodes well ahead of schedule. A huge thank you to our two main Service Node developers, [jcktm](https://github.com/jcktm/) and [Doy-lee](https://github.com/Doy-lee), who have been putting in long hours to get this out. This will mark the first time Proof of Service has been implemented on a CryptoNote coin and we’re really excited to have everyone onboard to test it out.\n\n**How will the rollout/update process work?**\n![1_r2ncvrAR0dbF2-tY-eF88Q.png](https://cdn.steemitimages.com/DQmNcpDfVjx3MzZc9niDEHhwpxig3P3bj64BC1TsJr2HtAP/1_r2ncvrAR0dbF2-tY-eF88Q.png)\nBeginning on 09/08/2018 (August 9th) the testnet will be restarted with Service Nodes enabled. The testnet will operate for two weeks in this state. During this period, we will make final changes to the Service Node software, fix bugs as they are reported to us, and add features which will be useful for the final release. Bugs found by community members in Service Node software will be rewarded with bounties at the discretion of the Loki team and depending on severity.\n\nOn 23/08/2018 (August 23rd) we anticipate the release of the final version of the Service node software, including any bug fixes/changes we found in the Service Node testnet period. This release marks a mandatory upgrade period between 23/08/2018 and 20/09/2018. In this period we will contact exchanges, pools, and miners. All clients will need to update their software. Testnet will continue operation with the new changes, however **on 20/09/2018 (September 20th) mainnet and stagenet will hard fork and Service Nodes will be released** in a production environment.\n\nService Nodes already set up on testnet will **NOT** rollover to mainnet, so when the mainnet forks everyone will have the same opportunity to begin operating a service node using real Loki.\n\n**What do Service Nodes do in this update?**\nAs part of the rollout process we need to slowly introduce Service Node functionality. In this upcoming fork, Service Nodes will only have the ability to register and receive rewards. There is no complex testing functionality yet enabled. In this fork Service Nodes will not route data other than propagating blockchain data to their peers. However to be rewarded, Service Nodes that are online automatically transmit pings to the network. If a ping is not submitted each hour a node is assumed to be offline and will be deregistered.\n\nMore complex functionality is being heavily developed as we speak and will be introduced to Service Nodes over the coming months. However, it is essential that we deploy the base functionality of Service Nodes before we can begin integrating more complex testing and begin routing packets on top of service nodes.\n\nRemaining features that will be introduced over the coming months:\n\nBlink (Instant Transactions)\nLokinet (Packet Routing & SNApps)\nLoki Messenger (Message Storage)\nEnforced Remote Nodes (Light Client Improvements)\n\n**How can I register a Service Node on testnet?**\nYou will need the alpha software from [here](https://github.com/loki-project/loki/releases), and instructions on how to use it are [here](https://github.com/jcktm/loki/blob/service-node-guide/service_node_guide.md), this also includes a guide on how pooled staking works. This guide assumes you know how the CLI and daemon work. If you don’t, a complete guide on staking is in the works, so sit tight!\n\nTo test Service Nodes, you will need:\n\n100 testnet Loki\nA VPS, or highly available home server\nThe Loki CLI wallet, and the Loki Daemon\nOn testnet, the staking requirement will be 100 Loki, so everyone can get in and test. We will distribute funds from the testnet foundation wallet, so just ping one of the admins in the Loki telegram or [discord](https://discord.gg/FkwRPSA) and we will send you some testnet Loki to stake. You can also mine testnet loki by running start_mining <address in lokid.\n\nWe’ve also shortened the staking duration to just 2 days in the testnet, so you should be able to test restaking over the next couple of weeks to familiarise yourself with the process.\n\nThis would also be a good time for anyone seeking to pool their staking requirement to test out how that functionality works. So jump on testnet and start testing.\n\n**How can I provide feedback or submit bugs?**\nFor general feedback and discussion about the software, you can go to the brand new [#service-node-testing discord channel](https://discord.gg/FkwRPSA).\n\nIf you spot bugs in the code or add features to it, you should submit an issue or pull request to [GitHub](https://github.com/loki-project/loki). The devs will review the bugand include any necessary fixes in the final release.\n\n**What are the requirements for setting up a Service Node on Mainnet?**\nWe have been testing various VPS providers across the course of the last few months and we will be making some recommendations based on positive experiences. In the beginning Service Node operators will have much more choice about where they set up their nodes due to the significantly lower stresses they face. When Loki Messenger and Lokinet are finished, the bandwidth requirements will become more onerous and low performance nodes will have to upgrade hardware and network connections or risk being kicked off the network by automated bandwidth testing systems. When a date for Lokinet is set, we will warn Service Node operators at least 30 days in advance so that they can upgrade their servers.\n\n**Where can I go for more information on Service Nodes?**\nWe are currently setting up a webpage to act as a central point for operators to stay updated with all of the latest information. This portal will be updated as we produce documentation on Service Nodes. We want to make setting up a Service Node as clear as possible, and provide in-depth explanations on how the process works, so operators don’t end up making expensive mistakes.\n\nWe are updating the channels in [discord](https://discord.gg/FkwRPSA) to include a dedicated Service Nodes category, so we can have more in-depth discussions about the software and provide support to those having difficulty.\n\nVery exciting times! Let’s get testing, LOKIGANG!\n\nOriginally published at [loki.network](https://loki.network/service-nodes-testnet-release-date-announced/).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"servicenodes\",\"loki\",\"lokinet\"],\"image\":[\"https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png\",\"https://cdn.steemitimages.com/DQmNcpDfVjx3MzZc9niDEHhwpxig3P3bj64BC1TsJr2HtAP/1_r2ncvrAR0dbF2-tY-eF88Q.png\"],\"links\":[\"https://github.com/jcktm/\",\"https://github.com/Doy-lee\",\"https://github.com/loki-project/loki/releases\",\"https://github.com/jcktm/loki/blob/service-node-guide/service_node_guide.md\",\"https://discord.gg/FkwRPSA\",\"https://github.com/loki-project/loki\",\"https://loki.network/service-nodes-testnet-release-date-announced/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "blockchain",
      "permlink": "service-nodes-testnet-announcement",
      "title": "Service Nodes Testnet Announcement"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T20:29:36",
  "trx_id": "bd75622712872e69f13400aa8d96151aef1e68ad",
  "trx_in_block": 3,
  "virtual_op": 0
}
2018/09/03 03:55:54
authorloki-network
permlinklaying-down-layer-one-loki
votersensation
weight10000 (100.00%)
Transaction InfoBlock #25625771/Trx d564a75ceaf700078b60ede3d80e8f37b4931d62
View Raw JSON Data
{
  "block": 25625771,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "laying-down-layer-one-loki",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T03:55:54",
  "trx_id": "d564a75ceaf700078b60ede3d80e8f37b4931d62",
  "trx_in_block": 5,
  "virtual_op": 0
}
2018/09/03 02:55:15
authorloki-network
permlinklaying-down-layer-one-loki
voterfastresteem
weight100 (1.00%)
Transaction InfoBlock #25624560/Trx 320e8d4868a6c884496b10a16f4bf32611f1f87e
View Raw JSON Data
{
  "block": 25624560,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "laying-down-layer-one-loki",
      "voter": "fastresteem",
      "weight": 100
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T02:55:15",
  "trx_id": "320e8d4868a6c884496b10a16f4bf32611f1f87e",
  "trx_in_block": 49,
  "virtual_op": 0
}
2018/09/03 02:55:06
authorloki-network
body![1_pn8abNlN6YDT88uRLDekaw.jpeg](https://cdn.steemitimages.com/DQmeYYUdvXUA49dJtkNTLjYUaxNAdk4XL7uucudVxbUkCGX/1_pn8abNlN6YDT88uRLDekaw.jpeg) Over the last three months, there has been significant focus on Loki’s layer two, with numerous papers and articles revealing the true scope of Loki’s Service Node functionality with Loki now becoming a fully fledged mixnet. There has also been much talk about how Loki as a currency, or layer one transactional medium, will function in this framework. Initially we envisioned Loki would act as an access token to prevent Sybil attacks, however there are some downfalls of that system which we addressed in an article here. Given we have focused so much on Loki’s second layer, it’s time to give Loki’s first layer some explanation, and demonstrate why Loki is not only an advancement in layer two design, but also what makes it a worthwhile cryptocurrency. A Move Towards Scaling Monero and most other Cryptonote coins have dynamically scaling block sizes, meaning there is no hard limit to how many transactions can theoretically take place on the blockchain. However in practice, nodes must transmit data between each other, and as each block is accepted into the network and the block size grows, low performance nodes can struggle to keep up with the higher bandwidth requirements and suffer computational stress trying to verify all transactions. This can centralise the operation of full nodes to miners, who make up one of the only parties that have an incentive to operate full nodes. If we can create a way to incentivise the operation of full nodes, we can avoid the aforementioned issues. This is one of the goals of Loki Service Nodes; to create a network of full nodes that are incentivised to hold and serve a full copy of the blockchain. These nodes must meet standards of service that are tested by a distributed method of flagging called Swarm Flagging. Because nodes are competing for a limited block reward and can be removed from the staking reward pool, they are always incentivised to serve copies of the blockchain to users and relay transactions. Theoretically, this means that Loki can scale to handle much larger blocks and thus, handle a higher transaction throughput. This is predicated on the fact that the full nodes operating on the Loki network offer higher bandwidth/storage and compute performance than nodes on the Bitcoin or Monero network. Instant Transactions with Blink In a typical blockchain system, the confirmation time for any given transaction is the time it takes for a transaction to be included in a block. However, because of competing miners, withheld blocks, and Finney attacks, recipients usually require a number of additional blocks to be created on top of the block which holds a transaction before it is considered to be complete.[1] Depending on a multitude of factors specific to each blockchain, this process can take 10–60 minutes, which is inconvenient for merchants and customers who must wait for confirmations before they release goods or commence services. Because of Loki’s Service Node architecture, near instant transactions are possible. Blink enables the same transactions that would occur on the Loki mainchain to be confirmed in seconds rather than minutes, assuring both the sender and the receiver of the validity of the transaction, and protecting the receiver against a double spend. Blink works in a similar fashion to DASH’s InstantSend.[2] However unlike DASH’s InstantSend, Loki maintains all of its privacy properties throughout the process. Any third party looking at a Blink transaction will have no idea of the amount, nor the address of the sender and receiver. This opens up a range of new use cases for Loki, where face-to-face payments become increasingly practical and online payments become quicker and easier for users. Stable and Formally Defined Funding Model Funding models for cryptocurrencies are generally tricky, weak and informal, and donation only models can lead to the creation of special interest groups like blockstream, Bitcoin Unlimited and Bitcoin ABC. These groups typically act as for profit companies who drive an agenda that might not align with the community as a whole. The downside to most formally defined models is they act as a sort of tax, either through emissions or some kind of fee. This can be seen to take choice away from users as they are unable to allocate their funds to the projects they see as important. Attempting to solve some of the aforementioned issues, Monero maintains a forum funding system, which is fully funded by a donations model. Projects vetted by the the Monero core team are featured on the Seeking Funding page, and users are free to donate Monero to projects they feel are worthy. The Monero core team also has an official donations wallet which often contributes large amounts of Monero to projects seeking funding. The advantage of the donations model is that users have full autonomy over how they spend their funds and what specific projects they support. However, there are also disadvantages to this model: funding is never guaranteed for high quality projects, and a large number of the projects receive about 1/5th of their donations from their ‘General Donations’ fund for Monero itself. The ability for a community like Monero to continue to self-fund and provide core contributions may decrease over time, and that’s something we want to avoid with Loki. Loki’s long-term funding model is quite different from the donations model used by the cryptocurrencies mentioned above, and we think it will provide a significant advantage to consistent development, which will be in the interest of our users. Proposed in the whitepaper V3 is a revised governance block reward, which allocates 5% of each block reward to fund governance operations. Of this, 5% block reward 3.75% is controlled by the Loki Foundation, a registered Australian non-profit which is legally bound to spend the block reward as per its constitution. “facilitating the development of an open source, highly secure, decentralised data transmission network that allows individuals, business and government to freely transact and communicate without the threat of malicious third party interference” The other 1.25% is controlled by the Service Nodes through the Loki funding system. The Loki funding system is an entirely non-custodial system of proposal funding, meaning the Loki Foundation cannot control how its funds are allocated. Because Service Nodes are not bound by Australian law or a constitution, this greatly expands the range of proposals that can be funded. To distribute funds to proposals, Service Nodes vote on proposals that occur on-chain, and funding is allocated every two months via special funding blocks which pay a portion of their block reward to proposal addresses. Because Service Nodes represent players with a high stake in the Loki system, they are incentivised to vote on proposals which will increase the value of their stake. Remote Node Availability Due to the design of all CryptoNote coins, the blockchain cannot be easily queried by connection to a full node. Instead of simple queries being made for the balances of public keys, full nodes must transmit full blocks to users, and the user has to scan every transaction in the block and identify whether they can calculate the private spend key for the destination stealth address. This results in significant stress being placed on every remote node operator with no reward, and Monero and other Cryptonote coins therefore rely on the altruism of community members to fund these operations, which can be problematic. It is common for mobile users in Monero to cycle through 3 or 4 remote nodes before connecting to one that is reliable. Additionally, as any user can become a remote node that serves blocks to the community, there is the possibility that “popular” remote nodes will provide an altered history of the blockchain. Though this altered history cannot be used to directly steal a user’s funds, in combination with other malicious attacks, a remote node could potentially convince a user to send funds twice to someone who has already received the transaction. By rewarding Service Nodes, Loki creates a large, decentralised network of nodes with a full copy of the blockchain. These nodes are incentivised to serve copies of the blockchain to users and relay transaction. If a user chooses to connect to these nodes at random, ‘popular’ nodes are no longer an issue. This also balances the load of remote syncing across the whole network instead of onto a select few nodes. Lokinet, SNApps and Highly Integrated Payments Work is ongoing on Lokinet, which when fully launched will be a private, decentralised and Sybil resistant overlay network for the internet. You can read a detailed article about it here. Anyone can host services on Lokinet, which will be called SNApps (Service Node Applications). With SNApps, any web developer will be able to host websites that are completely anonymous; the website owner won’t know the IP address of their visitors, and and the visitors won’t know the IP address of the website they connect to. All content hosted inside Lokinet will be accessible through the Loki browser. The Loki browser will have an inbuilt wallet. Users will be able to fund this wallet with Loki, and the browser will automatically hook into SNApps that display Loki addresses for payments. This will make it very easy for a user to operate a store, or take or make payments for goods and services while maintaining anonymity between both networking and transactional layers. Lokinet will also have exit functionality, so any website operator who serves a website on the wider internet will be able to implement these hooks for users of the Loki browser to easily manage Loki payments. In Summary Loki’s value is derived not only from an inventive layer two, but also as a layer one transactional medium, or cryptocurrency. Although Loki is moving away from the use of $LOKI as simply an access token, there are still some significant advantages to $LOKI over other privacy based coins. Most of these advantages are a result of the widely distributed set of Sybil resistant nodes, called Service Nodes. Due to Loki’s high scalability, Loki can handle a higher transaction throughput and offer higher bandwidth/storage and compute performance than nodes on the Bitcoin or Monero network. Leveraging Service Nodes, Loki can be sent near instantly and privately using Blink bringing instant new use-cases. Loki’s unique funding model provides strong governance and avoids the pitfalls and potential risks that donation-only models pose. Due to Loki’s incentivised Service Nodes, remote syncing loads are balanced across the whole network and the issues caused by ‘popular’ nodes are avoided. Layer one, coupled with an impressive layer two provides a whole suite of services to assist Loki users transact and communicate with absolute freedom. [1] “Irreversible Transactions — Bitcoin Wiki.” 15 Mar. 2018, https://en.bitcoin.it/wiki/Irreversible_Transactions. Accessed 25 Apr. 2018. [2] “Whitepaper · dashpay/dash Wiki · GitHub.” https://github.com/dashpay/dash/wiki/Whitepaper. Accessed 27 Jul. 2018. Originally published at loki.network.
json metadata{"tags":["loki","lokinet","layerone","layertwo","scaling"],"image":["https://cdn.steemitimages.com/DQmeYYUdvXUA49dJtkNTLjYUaxNAdk4XL7uucudVxbUkCGX/1_pn8abNlN6YDT88uRLDekaw.jpeg"],"links":["https://en.bitcoin.it/wiki/Irreversible_Transactions","https://github.com/dashpay/dash/wiki/Whitepaper"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkloki
permlinklaying-down-layer-one-loki
titleLaying Down Layer One: Loki
Transaction InfoBlock #25624557/Trx 6482e9d92cd6ef2bb483196b2ed20b5e59a9be26
View Raw JSON Data
{
  "block": 25624557,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "![1_pn8abNlN6YDT88uRLDekaw.jpeg](https://cdn.steemitimages.com/DQmeYYUdvXUA49dJtkNTLjYUaxNAdk4XL7uucudVxbUkCGX/1_pn8abNlN6YDT88uRLDekaw.jpeg)\nOver the last three months, there has been significant focus on Loki’s layer two, with numerous papers and articles revealing the true scope of Loki’s Service Node functionality with Loki now becoming a fully fledged mixnet. There has also been much talk about how Loki as a currency, or layer one transactional medium, will function in this framework. Initially we envisioned Loki would act as an access token to prevent Sybil attacks, however there are some downfalls of that system which we addressed in an article here. Given we have focused so much on Loki’s second layer, it’s time to give Loki’s first layer some explanation, and demonstrate why Loki is not only an advancement in layer two design, but also what makes it a worthwhile cryptocurrency.\n\nA Move Towards Scaling\nMonero and most other Cryptonote coins have dynamically scaling block sizes, meaning there is no hard limit to how many transactions can theoretically take place on the blockchain. However in practice, nodes must transmit data between each other, and as each block is accepted into the network and the block size grows, low performance nodes can struggle to keep up with the higher bandwidth requirements and suffer computational stress trying to verify all transactions. This can centralise the operation of full nodes to miners, who make up one of the only parties that have an incentive to operate full nodes.\n\nIf we can create a way to incentivise the operation of full nodes, we can avoid the aforementioned issues. This is one of the goals of Loki Service Nodes; to create a network of full nodes that are incentivised to hold and serve a full copy of the blockchain. These nodes must meet standards of service that are tested by a distributed method of flagging called Swarm Flagging. Because nodes are competing for a limited block reward and can be removed from the staking reward pool, they are always incentivised to serve copies of the blockchain to users and relay transactions.\n\nTheoretically, this means that Loki can scale to handle much larger blocks and thus, handle a higher transaction throughput. This is predicated on the fact that the full nodes operating on the Loki network offer higher bandwidth/storage and compute performance than nodes on the Bitcoin or Monero network.\n\nInstant Transactions with Blink\nIn a typical blockchain system, the confirmation time for any given transaction is the time it takes for a transaction to be included in a block. However, because of competing miners, withheld blocks, and Finney attacks, recipients usually require a number of additional blocks to be created on top of the block which holds a transaction before it is considered to be complete.[1] Depending on a multitude of factors specific to each blockchain, this process can take 10–60 minutes, which is inconvenient for merchants and customers who must wait for confirmations before they release goods or commence services.\n\nBecause of Loki’s Service Node architecture, near instant transactions are possible. Blink enables the same transactions that would occur on the Loki mainchain to be confirmed in seconds rather than minutes, assuring both the sender and the receiver of the validity of the transaction, and protecting the receiver against a double spend.\n\nBlink works in a similar fashion to DASH’s InstantSend.[2] However unlike DASH’s InstantSend, Loki maintains all of its privacy properties throughout the process. Any third party looking at a Blink transaction will have no idea of the amount, nor the address of the sender and receiver. This opens up a range of new use cases for Loki, where face-to-face payments become increasingly practical and online payments become quicker and easier for users.\n\nStable and Formally Defined Funding Model\nFunding models for cryptocurrencies are generally tricky, weak and informal, and donation only models can lead to the creation of special interest groups like blockstream, Bitcoin Unlimited and Bitcoin ABC. These groups typically act as for profit companies who drive an agenda that might not align with the community as a whole. The downside to most formally defined models is they act as a sort of tax, either through emissions or some kind of fee. This can be seen to take choice away from users as they are unable to allocate their funds to the projects they see as important.\n\nAttempting to solve some of the aforementioned issues, Monero maintains a forum funding system, which is fully funded by a donations model. Projects vetted by the the Monero core team are featured on the Seeking Funding page, and users are free to donate Monero to projects they feel are worthy. The Monero core team also has an official donations wallet which often contributes large amounts of Monero to projects seeking funding. The advantage of the donations model is that users have full autonomy over how they spend their funds and what specific projects they support. However, there are also disadvantages to this model: funding is never guaranteed for high quality projects, and a large number of the projects receive about 1/5th of their donations from their ‘General Donations’ fund for Monero itself. The ability for a community like Monero to continue to self-fund and provide core contributions may decrease over time, and that’s something we want to avoid with Loki.\n\nLoki’s long-term funding model is quite different from the donations model used by the cryptocurrencies mentioned above, and we think it will provide a significant advantage to consistent development, which will be in the interest of our users. Proposed in the whitepaper V3 is a revised governance block reward, which allocates 5% of each block reward to fund governance operations. Of this, 5% block reward 3.75% is controlled by the Loki Foundation, a registered Australian non-profit which is legally bound to spend the block reward as per its constitution.\n\n“facilitating the development of an open source, highly secure, decentralised data transmission network that allows individuals, business and government to freely transact and communicate without the threat of malicious third party interference”\nThe other 1.25% is controlled by the Service Nodes through the Loki funding system. The Loki funding system is an entirely non-custodial system of proposal funding, meaning the Loki Foundation cannot control how its funds are allocated. Because Service Nodes are not bound by Australian law or a constitution, this greatly expands the range of proposals that can be funded. To distribute funds to proposals, Service Nodes vote on proposals that occur on-chain, and funding is allocated every two months via special funding blocks which pay a portion of their block reward to proposal addresses. Because Service Nodes represent players with a high stake in the Loki system, they are incentivised to vote on proposals which will increase the value of their stake.\n\nRemote Node Availability\nDue to the design of all CryptoNote coins, the blockchain cannot be easily queried by connection to a full node. Instead of simple queries being made for the balances of public keys, full nodes must transmit full blocks to users, and the user has to scan every transaction in the block and identify whether they can calculate the private spend key for the destination stealth address. This results in significant stress being placed on every remote node operator with no reward, and Monero and other Cryptonote coins therefore rely on the altruism of community members to fund these operations, which can be problematic.\n\nIt is common for mobile users in Monero to cycle through 3 or 4 remote nodes before connecting to one that is reliable. Additionally, as any user can become a remote node that serves blocks to the community, there is the possibility that “popular” remote nodes will provide an altered history of the blockchain. Though this altered history cannot be used to directly steal a user’s funds, in combination with other malicious attacks, a remote node could potentially convince a user to send funds twice to someone who has already received the transaction.\n\nBy rewarding Service Nodes, Loki creates a large, decentralised network of nodes with a full copy of the blockchain. These nodes are incentivised to serve copies of the blockchain to users and relay transaction. If a user chooses to connect to these nodes at random, ‘popular’ nodes are no longer an issue. This also balances the load of remote syncing across the whole network instead of onto a select few nodes.\n\nLokinet, SNApps and Highly Integrated Payments\nWork is ongoing on Lokinet, which when fully launched will be a private, decentralised and Sybil resistant overlay network for the internet. You can read a detailed article about it here.\n\nAnyone can host services on Lokinet, which will be called SNApps (Service Node Applications). With SNApps, any web developer will be able to host websites that are completely anonymous; the website owner won’t know the IP address of their visitors, and and the visitors won’t know the IP address of the website they connect to. All content hosted inside Lokinet will be accessible through the Loki browser.\n\nThe Loki browser will have an inbuilt wallet. Users will be able to fund this wallet with Loki, and the browser will automatically hook into SNApps that display Loki addresses for payments. This will make it very easy for a user to operate a store, or take or make payments for goods and services while maintaining anonymity between both networking and transactional layers. Lokinet will also have exit functionality, so any website operator who serves a website on the wider internet will be able to implement these hooks for users of the Loki browser to easily manage Loki payments.\n\nIn Summary\nLoki’s value is derived not only from an inventive layer two, but also as a layer one transactional medium, or cryptocurrency. Although Loki is moving away from the use of $LOKI as simply an access token, there are still some significant advantages to $LOKI over other privacy based coins. Most of these advantages are a result of the widely distributed set of Sybil resistant nodes, called Service Nodes. Due to Loki’s high scalability, Loki can handle a higher transaction throughput and offer higher bandwidth/storage and compute performance than nodes on the Bitcoin or Monero network. Leveraging Service Nodes, Loki can be sent near instantly and privately using Blink bringing instant new use-cases. Loki’s unique funding model provides strong governance and avoids the pitfalls and potential risks that donation-only models pose. Due to Loki’s incentivised Service Nodes, remote syncing loads are balanced across the whole network and the issues caused by ‘popular’ nodes are avoided. Layer one, coupled with an impressive layer two provides a whole suite of services to assist Loki users transact and communicate with absolute freedom.\n\n[1] “Irreversible Transactions — Bitcoin Wiki.” 15 Mar. 2018, https://en.bitcoin.it/wiki/Irreversible_Transactions. Accessed 25 Apr. 2018.\n\n[2] “Whitepaper · dashpay/dash Wiki · GitHub.” https://github.com/dashpay/dash/wiki/Whitepaper. Accessed 27 Jul. 2018.\n\nOriginally published at loki.network.",
      "json_metadata": "{\"tags\":[\"loki\",\"lokinet\",\"layerone\",\"layertwo\",\"scaling\"],\"image\":[\"https://cdn.steemitimages.com/DQmeYYUdvXUA49dJtkNTLjYUaxNAdk4XL7uucudVxbUkCGX/1_pn8abNlN6YDT88uRLDekaw.jpeg\"],\"links\":[\"https://en.bitcoin.it/wiki/Irreversible_Transactions\",\"https://github.com/dashpay/dash/wiki/Whitepaper\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "loki",
      "permlink": "laying-down-layer-one-loki",
      "title": "Laying Down Layer One: Loki"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T02:55:06",
  "trx_id": "6482e9d92cd6ef2bb483196b2ed20b5e59a9be26",
  "trx_in_block": 29,
  "virtual_op": 0
}
2018/08/25 19:28:00
authorloki-network
permlinkwhy-add-a-2nd-layer-to-monero
votercarback1
weight10000 (100.00%)
Transaction InfoBlock #25385342/Trx 4feca1040f450615f6fccdf5e47b0483cae4762e
View Raw JSON Data
{
  "block": 25385342,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "why-add-a-2nd-layer-to-monero",
      "voter": "carback1",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-25T19:28:00",
  "trx_id": "4feca1040f450615f6fccdf5e47b0483cae4762e",
  "trx_in_block": 7,
  "virtual_op": 0
}
steemdelegated 18.553 SP to @loki-network
2018/08/09 09:22:09
delegateeloki-network
delegatorsteem
vesting shares30173.452524 VESTS
Transaction InfoBlock #24912606/Trx b1adca9bc76c2f12afea271b56aa2c508b6ae2bd
View Raw JSON Data
{
  "block": 24912606,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "loki-network",
      "delegator": "steem",
      "vesting_shares": "30173.452524 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-09T09:22:09",
  "trx_id": "b1adca9bc76c2f12afea271b56aa2c508b6ae2bd",
  "trx_in_block": 37,
  "virtual_op": 0
}
loki-networkreceived 0.004 STEEM, 0.001 SBD, 0.006 SP author reward for @loki-network / nkz81sxb
2018/07/31 14:58:09
authorloki-network
permlinknkz81sxb
sbd payout0.001 SBD
steem payout0.004 STEEM
vesting payout10.133987 VESTS
Transaction InfoBlock #24660246/Virtual Operation #4
View Raw JSON Data
{
  "block": 24660246,
  "op": [
    "author_reward",
    {
      "author": "loki-network",
      "permlink": "nkz81sxb",
      "sbd_payout": "0.001 SBD",
      "steem_payout": "0.004 STEEM",
      "vesting_payout": "10.133987 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-31T14:58:09",
  "trx_id": "0000000000000000000000000000000000000000",
  "trx_in_block": 4294967295,
  "virtual_op": 4
}
dtubereceived 0.004 SP benefactor reward from @loki-network
2018/07/31 14:58:09
authorloki-network
benefactordtube
permlinknkz81sxb
sbd payout0.000 SBD
steem payout0.000 STEEM
vesting payout6.080392 VESTS
Transaction InfoBlock #24660246/Virtual Operation #3
View Raw JSON Data
{
  "block": 24660246,
  "op": [
    "comment_benefactor_reward",
    {
      "author": "loki-network",
      "benefactor": "dtube",
      "permlink": "nkz81sxb",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "6.080392 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-31T14:58:09",
  "trx_id": "0000000000000000000000000000000000000000",
  "trx_in_block": 4294967295,
  "virtual_op": 3
}
2018/07/26 20:28:30
authorcheetah
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://coinlib.io/news/LOKI
json metadata
parent authorloki-network
parent permlinktldr-why-loki-should-change-its-emission-curve
permlinkcheetah-re-loki-networktldr-why-loki-should-change-its-emission-curve
title
Transaction InfoBlock #24523338/Trx 255127600177457a28bf818df09dfaa17ffd1014
View Raw JSON Data
{
  "block": 24523338,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://coinlib.io/news/LOKI",
      "json_metadata": "",
      "parent_author": "loki-network",
      "parent_permlink": "tldr-why-loki-should-change-its-emission-curve",
      "permlink": "cheetah-re-loki-networktldr-why-loki-should-change-its-emission-curve",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-26T20:28:30",
  "trx_id": "255127600177457a28bf818df09dfaa17ffd1014",
  "trx_in_block": 29,
  "virtual_op": 0
}
2018/07/26 20:28:27
authorloki-network
permlinktldr-why-loki-should-change-its-emission-curve
votercheetah
weight8 (0.08%)
Transaction InfoBlock #24523337/Trx 817b97221933c7849a457c300afbec62f7a92de5
View Raw JSON Data
{
  "block": 24523337,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "tldr-why-loki-should-change-its-emission-curve",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-26T20:28:27",
  "trx_id": "817b97221933c7849a457c300afbec62f7a92de5",
  "trx_in_block": 16,
  "virtual_op": 0
}
2018/07/26 20:28:18
authorloki-network
body![1_Kk1sC7bJozCnfpTkLhMD2g.png](https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png) This article is intended as a basic overview as to the reasoning behind changing Loki’s emission curve. To this purpose we have largely simplified the factors and influences at play; for a more in depth understanding, please refer to our paper [Loki Cryptoeconomics: Alterations to the Staking Requirements and the Emission Curve](http://loki.network/proposal). DISCLAIMER This article contains charts and figures which include examples of return of investments and prices for the Loki cryptographic coin. These prices are examples only and are not a prediction, forecast, or representation as to any actual likelihood of price movement of the Loki cryptographic coin. The payments shown in the examples below are general in nature and will only take effect if the planned hardfork occurs. Factors outside the control of Loki could impact what actual payments are made to Service Nodes. Those parties not operating a Service Node should not rely on these examples when deciding whether or not to participate in the Loki project. This article should be read together with the Loki whitepaper and full Loki Cryptoeconomic report. The main goals in changing the Loki emission curve are to: Maintain Loki’s [Sybil](https://en.wikipedia.org/wiki/Sybil_attack) attack resistance, by Ensuring that enough Service Nodes are incentivised to run, by Aiming to keep the return on investment (ROI) for running a Service Node at an acceptable level. The current emission curve is problematic because an excess of Loki is being produced which could lead to a large number of Service Nodes in the early years. While this doesn’t sound like a bad thing, considering our commitment to a decentralised network and Sybil resistance, it will become an issue when the Service Node rewards are split between too many Service Nodes. While the price of Loki fluctuates with the cryptocurrency market, real world costs in running a Service Node exist, and the reward each Service Node receives for running must be greater than the real world cost of running. In other words, Service Node operators must be making an acceptable profit, or there won’t be incentive for them to run. Chart 1 Chart 1 demonstrates that our current emission curve will result in many Service Nodes entering the network in the first few years, with the return on investment (ROI) quickly dropping below 0%. If too many Services Nodes run, the rewards are not worthwhile, and Services Nodes will leave resulting in a more centralised network. ![1_9dLSBnv9WyfodRGKvX3lQQ.png](https://cdn.steemitimages.com/DQmYNLpiqKrV2YMDxNCRjSKqBJZNgZXzBYcb2zNiCUYadU6/1_9dLSBnv9WyfodRGKvX3lQQ.png) Chart 2 Chart 2 depicts the effects of Loki’s proposed new emission curve, where there are less Service Nodes from the outset, but the return on investment (ROI) remains positive. This is better for the network in the long term because these Service Nodes will be continually incentivised to run (providing market-based Sybil resistance), while retaining a decentralised network. ![ch2.png](https://cdn.steemitimages.com/DQmRrMJWuQzUoZGY76m2VFBu5YpmNoDNw8ipU7X3d9AqY34/ch2.png) For further information regarding Loki Service Node game theory, and Loki Cryptoeconomics, please refer to the following reports: [Cryptoeconomics of the Loki Network](http://loki.network/cryptoeconomics) [Loki Cryptoeconomics](http://loki.network/proposal)
json metadata{"tags":["loki","sybilresistance","decentralized","servicenode","emission"],"image":["https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png","https://cdn.steemitimages.com/DQmYNLpiqKrV2YMDxNCRjSKqBJZNgZXzBYcb2zNiCUYadU6/1_9dLSBnv9WyfodRGKvX3lQQ.png","https://cdn.steemitimages.com/DQmRrMJWuQzUoZGY76m2VFBu5YpmNoDNw8ipU7X3d9AqY34/ch2.png"],"links":["http://loki.network/proposal","https://en.wikipedia.org/wiki/Sybil_attack","http://loki.network/cryptoeconomics"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkloki
permlinktldr-why-loki-should-change-its-emission-curve
titleTLDR: Why Loki Should Change its Emission Curve.
Transaction InfoBlock #24523334/Trx 07fa2f32836f7fa92210eeac8701f0c276a94cbe
View Raw JSON Data
{
  "block": 24523334,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "![1_Kk1sC7bJozCnfpTkLhMD2g.png](https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png)\n\nThis article is intended as a basic overview as to the reasoning behind changing Loki’s emission curve. To this purpose we have largely simplified the factors and influences at play; for a more in depth understanding, please refer to our paper [Loki Cryptoeconomics: Alterations to the Staking Requirements and the Emission Curve](http://loki.network/proposal).\n\nDISCLAIMER\n\nThis article contains charts and figures which include examples of return of investments and prices for the Loki cryptographic coin. These prices are examples only and are not a prediction, forecast, or representation as to any actual likelihood of price movement of the Loki cryptographic coin. The payments shown in the examples below are general in nature and will only take effect if the planned hardfork occurs. Factors outside the control of Loki could impact what actual payments are made to Service Nodes. Those parties not operating a Service Node should not rely on these examples when deciding whether or not to participate in the Loki project. This article should be read together with the Loki whitepaper and full Loki Cryptoeconomic report.\n\nThe main goals in changing the Loki emission curve are to:\n\nMaintain Loki’s [Sybil](https://en.wikipedia.org/wiki/Sybil_attack) attack resistance, by\nEnsuring that enough Service Nodes are incentivised to run, by\nAiming to keep the return on investment (ROI) for running a Service Node at an acceptable level.\nThe current emission curve is problematic because an excess of Loki is being produced which could lead to a large number of Service Nodes in the early years. While this doesn’t sound like a bad thing, considering our commitment to a decentralised network and Sybil resistance, it will become an issue when the Service Node rewards are split between too many Service Nodes.\n\nWhile the price of Loki fluctuates with the cryptocurrency market, real world costs in running a Service Node exist, and the reward each Service Node receives for running must be greater than the real world cost of running. In other words, Service Node operators must be making an acceptable profit, or there won’t be incentive for them to run.\n\n\nChart 1\nChart 1 demonstrates that our current emission curve will result in many Service Nodes entering the network in the first few years, with the return on investment (ROI) quickly dropping below 0%. If too many Services Nodes run, the rewards are not worthwhile, and Services Nodes will leave resulting in a more centralised network.\n\n![1_9dLSBnv9WyfodRGKvX3lQQ.png](https://cdn.steemitimages.com/DQmYNLpiqKrV2YMDxNCRjSKqBJZNgZXzBYcb2zNiCUYadU6/1_9dLSBnv9WyfodRGKvX3lQQ.png)\n\nChart 2\nChart 2 depicts the effects of Loki’s proposed new emission curve, where there are less Service Nodes from the outset, but the return on investment (ROI) remains positive. This is better for the network in the long term because these Service Nodes will be continually incentivised to run (providing market-based Sybil resistance), while retaining a decentralised network.\n\n![ch2.png](https://cdn.steemitimages.com/DQmRrMJWuQzUoZGY76m2VFBu5YpmNoDNw8ipU7X3d9AqY34/ch2.png)\n\nFor further information regarding Loki Service Node game theory, and Loki Cryptoeconomics, please refer to the following reports:\n\n[Cryptoeconomics of the Loki Network](http://loki.network/cryptoeconomics)\n\n[Loki Cryptoeconomics](http://loki.network/proposal)",
      "json_metadata": "{\"tags\":[\"loki\",\"sybilresistance\",\"decentralized\",\"servicenode\",\"emission\"],\"image\":[\"https://cdn.steemitimages.com/DQmSUBCSQ8LGLEEwLBGKgXL9vkjQvpLtz1NV8wSLXwotyyo/1_Kk1sC7bJozCnfpTkLhMD2g.png\",\"https://cdn.steemitimages.com/DQmYNLpiqKrV2YMDxNCRjSKqBJZNgZXzBYcb2zNiCUYadU6/1_9dLSBnv9WyfodRGKvX3lQQ.png\",\"https://cdn.steemitimages.com/DQmRrMJWuQzUoZGY76m2VFBu5YpmNoDNw8ipU7X3d9AqY34/ch2.png\"],\"links\":[\"http://loki.network/proposal\",\"https://en.wikipedia.org/wiki/Sybil_attack\",\"http://loki.network/cryptoeconomics\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "loki",
      "permlink": "tldr-why-loki-should-change-its-emission-curve",
      "title": "TLDR: Why Loki Should Change its Emission Curve."
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-26T20:28:18",
  "trx_id": "07fa2f32836f7fa92210eeac8701f0c276a94cbe",
  "trx_in_block": 9,
  "virtual_op": 0
}
2018/07/25 03:56:39
authorsteemitboard
bodyCongratulations @loki-network! You have completed the following achievement on Steemit and have been rewarded with new badge(s) : [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/posts.png)](http://steemitboard.com/@loki-network) Award for the number of posts published [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/voted.png)](http://steemitboard.com/@loki-network) Award for the number of upvotes received [![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/post4day.png)](http://steemitboard.com/@loki-network) You published 4 posts in one day <sub>_Click on the badge to view your Board of Honor._</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authorloki-network
parent permlinkm7x6k81n
permlinksteemitboard-notify-loki-network-20180725t035641000z
title
Transaction InfoBlock #24474760/Trx d778bf99d17b4d10c1d3c7752dfb137650323db6
View Raw JSON Data
{
  "block": 24474760,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @loki-network! You have completed the following achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/posts.png)](http://steemitboard.com/@loki-network) Award for the number of posts published\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/voted.png)](http://steemitboard.com/@loki-network) Award for the number of upvotes received\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/post4day.png)](http://steemitboard.com/@loki-network) You published 4 posts in one day\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "loki-network",
      "parent_permlink": "m7x6k81n",
      "permlink": "steemitboard-notify-loki-network-20180725t035641000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-25T03:56:39",
  "trx_id": "d778bf99d17b4d10c1d3c7752dfb137650323db6",
  "trx_in_block": 30,
  "virtual_op": 0
}
2018/07/24 15:49:12
authorloki-network
permlinknkz81sxb
voterencryptdcouple
weight10000 (100.00%)
Transaction InfoBlock #24460217/Trx e4fc05053bdb32274779cc4292463ad7e367f681
View Raw JSON Data
{
  "block": 24460217,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "nkz81sxb",
      "voter": "encryptdcouple",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T15:49:12",
  "trx_id": "e4fc05053bdb32274779cc4292463ad7e367f681",
  "trx_in_block": 77,
  "virtual_op": 0
}
2018/07/24 15:05:42
authorloki-network
permlinkm7x6k81n
voterhackerzizon
weight100 (1.00%)
Transaction InfoBlock #24459348/Trx f7ae7ea3b2b56d2bc895c8e10389351f0c8a0338
View Raw JSON Data
{
  "block": 24459348,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "m7x6k81n",
      "voter": "hackerzizon",
      "weight": 100
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T15:05:42",
  "trx_id": "f7ae7ea3b2b56d2bc895c8e10389351f0c8a0338",
  "trx_in_block": 42,
  "virtual_op": 0
}
loki-networkupdated options for m7x6k81n
2018/07/24 15:04:45
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":2500}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlinkm7x6k81n
Transaction InfoBlock #24459329/Trx c821d6a8fa35a5ef36670342653a170904d13307
View Raw JSON Data
{
  "block": 24459329,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 2500
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "m7x6k81n"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T15:04:45",
  "trx_id": "c821d6a8fa35a5ef36670342653a170904d13307",
  "trx_in_block": 38,
  "virtual_op": 0
}
loki-networkpublished a new post: m7x6k81n
2018/07/24 15:04:45
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/m7x6k81n'><img src='https://ipfs.io/ipfs/QmaYg3WUFjXrEr5m3ra1VRa3DhP2vjVcpz8Eoct1oYYjER'></a></center><hr> By CINELIXIR _________________________________________________________________ WEBSITE https://loki.network REDDIT https://www.reddit.com/r/LokiProject/ TWITTER https://twitter.com/loki_project BTC https://bitcointalk.org/index.php?top... DISCORD https://discordapp.com/invite/67GXfD6 TELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TV... <hr><a href='https://d.tube/#!/v/loki-network/m7x6k81n'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmfMiCxcMRwz4r9gsKpm8pNSYxYJdnvcKrLgva18SZw8Wh'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"LOKI Launch Party","snaphash":"QmPWmSa7sNukpdVnB5pntND2PNmbvuZnnEfzta7CYXVswt","author":"loki-network","permlink":"m7x6k81n","duration":91.742041,"filesize":13143247,"spritehash":"QmWYMSpGgxGs76JfZatHvv4X5ak7mmpvF6ihrwDryMTo1j"},"content":{"videohash":"QmfMiCxcMRwz4r9gsKpm8pNSYxYJdnvcKrLgva18SZw8Wh","description":"By CINELIXIR\n\n_________________________________________________________________\nWEBSITE https://loki.network\nREDDIT https://www.reddit.com/r/LokiProject/\nTWITTER https://twitter.com/loki_project\nBTC https://bitcointalk.org/index.php?top...\nDISCORD https://discordapp.com/invite/67GXfD6\nTELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TV...","tags":["launchparty","loki","cryptocurrency","blockchain"],"video240hash":"QmZExSHPB25XRz3P34FP6t1DPyd1u7qv5ig5ArfJEiMti3","video480hash":"QmV5cLDHwmcAgXA61poqemYC52SKJCni1ryYqinwfwdXqi"}},"tags":["launchparty","loki","cryptocurrency","blockchain","dtube"],"app":"dtube/0.7"}
parent author
parent permlinklaunchparty
permlinkm7x6k81n
titleLOKI Launch Party
Transaction InfoBlock #24459329/Trx c821d6a8fa35a5ef36670342653a170904d13307
View Raw JSON Data
{
  "block": 24459329,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/m7x6k81n'><img src='https://ipfs.io/ipfs/QmaYg3WUFjXrEr5m3ra1VRa3DhP2vjVcpz8Eoct1oYYjER'></a></center><hr>\n\nBy CINELIXIR\n\n_________________________________________________________________\nWEBSITE      https://loki.network\nREDDIT         https://www.reddit.com/r/LokiProject/\nTWITTER      https://twitter.com/loki_project\nBTC               https://bitcointalk.org/index.php?top...\nDISCORD      https://discordapp.com/invite/67GXfD6\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TV...\n\n<hr><a href='https://d.tube/#!/v/loki-network/m7x6k81n'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmfMiCxcMRwz4r9gsKpm8pNSYxYJdnvcKrLgva18SZw8Wh'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"LOKI Launch Party\",\"snaphash\":\"QmPWmSa7sNukpdVnB5pntND2PNmbvuZnnEfzta7CYXVswt\",\"author\":\"loki-network\",\"permlink\":\"m7x6k81n\",\"duration\":91.742041,\"filesize\":13143247,\"spritehash\":\"QmWYMSpGgxGs76JfZatHvv4X5ak7mmpvF6ihrwDryMTo1j\"},\"content\":{\"videohash\":\"QmfMiCxcMRwz4r9gsKpm8pNSYxYJdnvcKrLgva18SZw8Wh\",\"description\":\"By CINELIXIR\\n\\n_________________________________________________________________\\nWEBSITE      https://loki.network\\nREDDIT         https://www.reddit.com/r/LokiProject/\\nTWITTER      https://twitter.com/loki_project\\nBTC               https://bitcointalk.org/index.php?top...\\nDISCORD      https://discordapp.com/invite/67GXfD6\\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TV...\",\"tags\":[\"launchparty\",\"loki\",\"cryptocurrency\",\"blockchain\"],\"video240hash\":\"QmZExSHPB25XRz3P34FP6t1DPyd1u7qv5ig5ArfJEiMti3\",\"video480hash\":\"QmV5cLDHwmcAgXA61poqemYC52SKJCni1ryYqinwfwdXqi\"}},\"tags\":[\"launchparty\",\"loki\",\"cryptocurrency\",\"blockchain\",\"dtube\"],\"app\":\"dtube/0.7\"}",
      "parent_author": "",
      "parent_permlink": "launchparty",
      "permlink": "m7x6k81n",
      "title": "LOKI Launch Party"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T15:04:45",
  "trx_id": "c821d6a8fa35a5ef36670342653a170904d13307",
  "trx_in_block": 38,
  "virtual_op": 0
}
loki-networkupdated options for nkz81sxb
2018/07/24 14:58:09
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":2500}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlinknkz81sxb
Transaction InfoBlock #24459198/Trx aa326646e7b3a02227cd0c213486daeadea76ca0
View Raw JSON Data
{
  "block": 24459198,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 2500
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "nkz81sxb"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:58:09",
  "trx_id": "aa326646e7b3a02227cd0c213486daeadea76ca0",
  "trx_in_block": 8,
  "virtual_op": 0
}
loki-networkpublished a new post: nkz81sxb
2018/07/24 14:58:09
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/nkz81sxb'><img src='https://ipfs.io/ipfs/QmTXe7n6MzzFrBGHg7R4Exa7Pbdf6r2Zt2HB8NaHMfYPWi'></a></center><hr> LOKI LAUNCH PARTY PANEL: Creating A Crypto Simon Harman - Project Lead Kee Jefferys - Tech Lead Josh Jessop-Smith - Marketing Lead Chris McCabe - Operations Lead James Eddington - Moderator 0:44 How did you all meet and how did Loki start? 2:02 Who came up with the name Loki? 4:00 What was fundraising like for Loki? 7:34 How did the mainnet launch go? 9:47 What is on the Loki roadmap in the next 6 months? 14:07 Why is privacy something important? 17:00 What is the estimated time that Service Node functionality is live? 17:45 What were the key challenges for raising via private sale? 21:11 How do you guys plan to create network effects and grow Loki Messenger? 21:16 Who are your competitors? 23:02 Tell us, how is Loki different from Orchid Protocol? 25:00 Any exciting SNApps in the works? 27:00 What will be the second SNApp (Loki Service)? 28:05 About memes 29:15 Partnerships **Spot the CHAIRDROP _________________________________________________________________ WEBSITE https://loki.network REDDIT https://www.reddit.com/r/LokiProject/ TWITTER https://twitter.com/loki_project BTC https://bitcointalk.org/index.php?topic=3016125.0 DISCORD https://discordapp.com/invite/67GXfD6 TELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TVSQjCsZQ <hr><a href='https://d.tube/#!/v/loki-network/nkz81sxb'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmVeJvJiAs1mE11KWEieHZx6xLAv8KAkZPUQDFPP9qCm3s'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"Creating A Crypto","snaphash":"QmV4J8HTqm9tv25djL6pa31cW8hEoXy98mQvmV7Pc7hMun","author":"loki-network","permlink":"nkz81sxb","duration":1931.528707,"filesize":177494985,"spritehash":""},"content":{"videohash":"QmVeJvJiAs1mE11KWEieHZx6xLAv8KAkZPUQDFPP9qCm3s","description":"LOKI LAUNCH PARTY\nPANEL: Creating A Crypto\n\nSimon Harman - Project Lead\nKee Jefferys - Tech Lead\nJosh Jessop-Smith - Marketing Lead\nChris McCabe - Operations Lead\nJames Eddington - Moderator\n\n0:44 How did you all meet and how did Loki start?\n2:02 Who came up with the name Loki?\n4:00 What was fundraising like for Loki?\n7:34 How did the mainnet launch go?\n9:47 What is on the Loki roadmap in the next 6 months?\n14:07 Why is privacy something important?\n17:00 What is the estimated time that Service Node functionality is live?\n17:45 What were the key challenges for raising via private sale?\n21:11 How do you guys plan to create network effects and grow Loki Messenger?\n21:16 Who are your competitors?\n23:02 Tell us, how is Loki different from Orchid Protocol?\n25:00 Any exciting SNApps in the works?\n27:00 What will be the second SNApp (Loki Service)?\n28:05 About memes\n29:15 Partnerships\n\n**Spot the CHAIRDROP\n\n_________________________________________________________________\nWEBSITE https://loki.network\nREDDIT https://www.reddit.com/r/LokiProject/\nTWITTER https://twitter.com/loki_project\nBTC https://bitcointalk.org/index.php?topic=3016125.0\nDISCORD https://discordapp.com/invite/67GXfD6\nTELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TVSQjCsZQ","tags":["launchparty","loki","blockchain","panel"]}},"tags":["launchparty","loki","blockchain","panel","dtube"],"app":"dtube/0.7"}
parent author
parent permlinklaunchparty
permlinknkz81sxb
titleCreating A Crypto
Transaction InfoBlock #24459198/Trx aa326646e7b3a02227cd0c213486daeadea76ca0
View Raw JSON Data
{
  "block": 24459198,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/nkz81sxb'><img src='https://ipfs.io/ipfs/QmTXe7n6MzzFrBGHg7R4Exa7Pbdf6r2Zt2HB8NaHMfYPWi'></a></center><hr>\n\nLOKI LAUNCH PARTY\nPANEL: Creating A Crypto\n\nSimon Harman - Project Lead\nKee Jefferys - Tech Lead\nJosh Jessop-Smith - Marketing Lead\nChris McCabe - Operations Lead\nJames Eddington - Moderator\n\n0:44 How did you all meet and how did Loki start?\n2:02 Who came up with the name Loki?\n4:00 What was fundraising like for Loki?\n7:34 How did the mainnet launch go?\n9:47 What is on the Loki roadmap in the next 6 months?\n14:07 Why is privacy something important?\n17:00 What is the estimated time that Service Node functionality is live?\n17:45 What were the key challenges for raising via private sale?\n21:11 How do you guys plan to create network effects and grow Loki Messenger?\n21:16 Who are your competitors?\n23:02 Tell us, how is Loki different from Orchid Protocol?\n25:00 Any exciting SNApps in the works?\n27:00 What will be the second SNApp (Loki Service)?\n28:05 About memes\n29:15 Partnerships\n\n**Spot the CHAIRDROP\n\n_________________________________________________________________\nWEBSITE      https://loki.network\nREDDIT         https://www.reddit.com/r/LokiProject/\nTWITTER      https://twitter.com/loki_project\nBTC               https://bitcointalk.org/index.php?topic=3016125.0\nDISCORD      https://discordapp.com/invite/67GXfD6\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TVSQjCsZQ\n\n<hr><a href='https://d.tube/#!/v/loki-network/nkz81sxb'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmVeJvJiAs1mE11KWEieHZx6xLAv8KAkZPUQDFPP9qCm3s'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"Creating A Crypto\",\"snaphash\":\"QmV4J8HTqm9tv25djL6pa31cW8hEoXy98mQvmV7Pc7hMun\",\"author\":\"loki-network\",\"permlink\":\"nkz81sxb\",\"duration\":1931.528707,\"filesize\":177494985,\"spritehash\":\"\"},\"content\":{\"videohash\":\"QmVeJvJiAs1mE11KWEieHZx6xLAv8KAkZPUQDFPP9qCm3s\",\"description\":\"LOKI LAUNCH PARTY\\nPANEL: Creating A Crypto\\n\\nSimon Harman - Project Lead\\nKee Jefferys - Tech Lead\\nJosh Jessop-Smith - Marketing Lead\\nChris McCabe - Operations Lead\\nJames Eddington - Moderator\\n\\n0:44 How did you all meet and how did Loki start?\\n2:02 Who came up with the name Loki?\\n4:00 What was fundraising like for Loki?\\n7:34 How did the mainnet launch go?\\n9:47 What is on the Loki roadmap in the next 6 months?\\n14:07 Why is privacy something important?\\n17:00 What is the estimated time that Service Node functionality is live?\\n17:45 What were the key challenges for raising via private sale?\\n21:11 How do you guys plan to create network effects and grow Loki Messenger?\\n21:16 Who are your competitors?\\n23:02 Tell us, how is Loki different from Orchid Protocol?\\n25:00 Any exciting SNApps in the works?\\n27:00 What will be the second SNApp (Loki Service)?\\n28:05 About memes\\n29:15 Partnerships\\n\\n**Spot the CHAIRDROP\\n\\n_________________________________________________________________\\nWEBSITE      https://loki.network\\nREDDIT         https://www.reddit.com/r/LokiProject/\\nTWITTER      https://twitter.com/loki_project\\nBTC               https://bitcointalk.org/index.php?topic=3016125.0\\nDISCORD      https://discordapp.com/invite/67GXfD6\\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TVSQjCsZQ\",\"tags\":[\"launchparty\",\"loki\",\"blockchain\",\"panel\"]}},\"tags\":[\"launchparty\",\"loki\",\"blockchain\",\"panel\",\"dtube\"],\"app\":\"dtube/0.7\"}",
      "parent_author": "",
      "parent_permlink": "launchparty",
      "permlink": "nkz81sxb",
      "title": "Creating A Crypto"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:58:09",
  "trx_id": "aa326646e7b3a02227cd0c213486daeadea76ca0",
  "trx_in_block": 8,
  "virtual_op": 0
}
loki-networkupdated options for 5n9yhpgj
2018/07/24 14:42:18
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":2500}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlink5n9yhpgj
Transaction InfoBlock #24458881/Trx fd8109500d1ee5d62aba806f006ae4ed6767c3b4
View Raw JSON Data
{
  "block": 24458881,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 2500
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "5n9yhpgj"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:42:18",
  "trx_id": "fd8109500d1ee5d62aba806f006ae4ed6767c3b4",
  "trx_in_block": 14,
  "virtual_op": 0
}
loki-networkpublished a new post: 5n9yhpgj
2018/07/24 14:42:18
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/5n9yhpgj'><img src='https://ipfs.io/ipfs/QmWyB1YWLNLn1jyRpbkMozJkVvc2dZHCWuwcvviTG1mdLY'></a></center><hr> Breaking down the differences between blockchain forks and code forks with Kee Jefferys. _________________________________________________________________ WEBSITE https://loki.network REDDIT https://www.reddit.com/r/LokiProject/ TWITTER https://twitter.com/loki_project BTC https://bitcointalk.org/index.php?top... DISCORD https://discordapp.com/invite/67GXfD6 TELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TV... <hr><a href='https://d.tube/#!/v/loki-network/5n9yhpgj'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmeNgoBRzGMPbbTQurZbV8krnWwpa8HdvbuPaA6HiLpV7K'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"The Difference Between a Blockchain Fork and Code Fork","snaphash":"QmWSJjTf98nFPPQCev4GvRWFzdq2fpCainNEsFaQkwV74q","author":"loki-network","permlink":"5n9yhpgj","duration":107.136871,"filesize":17441923,"spritehash":"QmSpJ6tz8p1LATTSEq9hQS6sSPvHGNJajE4cKUbhtNicUn"},"content":{"videohash":"QmeNgoBRzGMPbbTQurZbV8krnWwpa8HdvbuPaA6HiLpV7K","description":"Breaking down the differences between blockchain forks and code forks with Kee Jefferys.\n\n_________________________________________________________________\nWEBSITE https://loki.network\nREDDIT https://www.reddit.com/r/LokiProject/\nTWITTER https://twitter.com/loki_project\nBTC https://bitcointalk.org/index.php?top...\nDISCORD https://discordapp.com/invite/67GXfD6\nTELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TV...","tags":["hardfork","cryptocurrency","softfork","loki"],"video240hash":"Qmb1z4ynuXfr1F2o6ssuzy8A36YV5mSrwkgKdiPVuD4Mha","video480hash":"QmcbNcPpd3vQqYKmBg3ydJcCCuX29HmSd8fkmYcrvujn1Q"}},"tags":["hardfork","cryptocurrency","softfork","loki","dtube"],"app":"dtube/0.7"}
parent author
parent permlinkhardfork
permlink5n9yhpgj
titleThe Difference Between a Blockchain Fork and Code Fork
Transaction InfoBlock #24458881/Trx fd8109500d1ee5d62aba806f006ae4ed6767c3b4
View Raw JSON Data
{
  "block": 24458881,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/5n9yhpgj'><img src='https://ipfs.io/ipfs/QmWyB1YWLNLn1jyRpbkMozJkVvc2dZHCWuwcvviTG1mdLY'></a></center><hr>\n\nBreaking down the differences between blockchain forks and code forks with Kee Jefferys.\n\n_________________________________________________________________\nWEBSITE      https://loki.network\nREDDIT         https://www.reddit.com/r/LokiProject/\nTWITTER      https://twitter.com/loki_project\nBTC               https://bitcointalk.org/index.php?top...\nDISCORD      https://discordapp.com/invite/67GXfD6\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TV...\n\n<hr><a href='https://d.tube/#!/v/loki-network/5n9yhpgj'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmeNgoBRzGMPbbTQurZbV8krnWwpa8HdvbuPaA6HiLpV7K'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"The Difference Between a Blockchain Fork and Code Fork\",\"snaphash\":\"QmWSJjTf98nFPPQCev4GvRWFzdq2fpCainNEsFaQkwV74q\",\"author\":\"loki-network\",\"permlink\":\"5n9yhpgj\",\"duration\":107.136871,\"filesize\":17441923,\"spritehash\":\"QmSpJ6tz8p1LATTSEq9hQS6sSPvHGNJajE4cKUbhtNicUn\"},\"content\":{\"videohash\":\"QmeNgoBRzGMPbbTQurZbV8krnWwpa8HdvbuPaA6HiLpV7K\",\"description\":\"Breaking down the differences between blockchain forks and code forks with Kee Jefferys.\\n\\n_________________________________________________________________\\nWEBSITE      https://loki.network\\nREDDIT         https://www.reddit.com/r/LokiProject/\\nTWITTER      https://twitter.com/loki_project\\nBTC               https://bitcointalk.org/index.php?top...\\nDISCORD      https://discordapp.com/invite/67GXfD6\\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TV...\",\"tags\":[\"hardfork\",\"cryptocurrency\",\"softfork\",\"loki\"],\"video240hash\":\"Qmb1z4ynuXfr1F2o6ssuzy8A36YV5mSrwkgKdiPVuD4Mha\",\"video480hash\":\"QmcbNcPpd3vQqYKmBg3ydJcCCuX29HmSd8fkmYcrvujn1Q\"}},\"tags\":[\"hardfork\",\"cryptocurrency\",\"softfork\",\"loki\",\"dtube\"],\"app\":\"dtube/0.7\"}",
      "parent_author": "",
      "parent_permlink": "hardfork",
      "permlink": "5n9yhpgj",
      "title": "The Difference Between a Blockchain Fork and Code Fork"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:42:18",
  "trx_id": "fd8109500d1ee5d62aba806f006ae4ed6767c3b4",
  "trx_in_block": 14,
  "virtual_op": 0
}
2018/07/24 14:29:03
authormagic8ball
bodyTo the question in your title, my Magic 8-Ball says:<blockquote>As I see it, yes</blockquote><hr>*Hi! I'm a bot, and this answer was posted automatically. Check [this post out](https://steemit.com/introduceyourself/@magic8ball/introducing-the-magic-8-ball-bot) for more information.*
json metadata{"tags":["test"],"app":"steemjs/examples"}
parent authorloki-network
parent permlinkn9l3w61s
permlink20180724t142904323z
title
Transaction InfoBlock #24458616/Trx d4e7ca4a2575737694c09d2fede007dedccb9422
View Raw JSON Data
{
  "block": 24458616,
  "op": [
    "comment",
    {
      "author": "magic8ball",
      "body": "To the question in your title, my Magic 8-Ball says:<blockquote>As I see it, yes</blockquote><hr>*Hi! I'm a bot, and this answer was posted automatically. Check [this post out](https://steemit.com/introduceyourself/@magic8ball/introducing-the-magic-8-ball-bot) for more information.*",
      "json_metadata": "{\"tags\":[\"test\"],\"app\":\"steemjs/examples\"}",
      "parent_author": "loki-network",
      "parent_permlink": "n9l3w61s",
      "permlink": "20180724t142904323z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:29:03",
  "trx_id": "d4e7ca4a2575737694c09d2fede007dedccb9422",
  "trx_in_block": 48,
  "virtual_op": 0
}
loki-networkupdated options for n9l3w61s
2018/07/24 14:28:57
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":2500}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlinkn9l3w61s
Transaction InfoBlock #24458614/Trx 203d22df7f32c269c29e40af9bb9f4d02e2e91c2
View Raw JSON Data
{
  "block": 24458614,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 2500
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "n9l3w61s"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:28:57",
  "trx_id": "203d22df7f32c269c29e40af9bb9f4d02e2e91c2",
  "trx_in_block": 1,
  "virtual_op": 0
}
loki-networkpublished a new post: n9l3w61s
2018/07/24 14:28:57
authorloki-network
body<center><a href='https://d.tube/#!/v/loki-network/n9l3w61s'><img src='https://ipfs.io/ipfs/Qma3bg5caUeNkLMWcMXrYcd7w1YMnfj5wL2qUWrxyLZCy4'></a></center><hr> _________________________________________________________________ WEBSITE https://loki.network REDDIT https://www.reddit.com/r/LokiProject/ TWITTER https://twitter.com/loki_project BTC https://bitcointalk.org/index.php?top... DISCORD https://discordapp.com/invite/67GXfD6 TELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TV... <hr><a href='https://d.tube/#!/v/loki-network/n9l3w61s'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmcD1y8NiPWC9t15tYdyzvtxPBGaJ6BpHduFJKycethDYt'> ▶️ IPFS</a>
json metadata{"video":{"info":{"title":"Are ASICS A Good Thing?","snaphash":"QmYSX1DmxskrDpzQvEXnFXwDL22Q1uizydpZjqKoHkFQZm","author":"loki-network","permlink":"n9l3w61s","duration":224.444082,"filesize":21608557,"spritehash":"QmaMWidN557Bue2MDdTd7LZbbvjQDK3Ru7Hrks9u3iEW4x"},"content":{"videohash":"QmcD1y8NiPWC9t15tYdyzvtxPBGaJ6BpHduFJKycethDYt","description":"_________________________________________________________________\nWEBSITE https://loki.network\nREDDIT https://www.reddit.com/r/LokiProject/\nTWITTER https://twitter.com/loki_project\nBTC https://bitcointalk.org/index.php?top...\nDISCORD https://discordapp.com/invite/67GXfD6\nTELEGRAM https://t.me/joinchat/DeNvR0JJ4JPn6TV...","tags":["loki","fpga","asic","centralization"],"video240hash":"QmTfRQL4tNFTk1xcHHr1sVu28T2VPb7dxszE1zaxK12S6H","video480hash":"QmQiqH9K8b78H8b4VEeCtXScCYqteTN3khmCvxb9cCx6tc"}},"tags":["loki","fpga","asic","centralization","dtube"],"app":"dtube/0.7"}
parent author
parent permlinkloki
permlinkn9l3w61s
titleAre ASICS A Good Thing?
Transaction InfoBlock #24458614/Trx 203d22df7f32c269c29e40af9bb9f4d02e2e91c2
View Raw JSON Data
{
  "block": 24458614,
  "op": [
    "comment",
    {
      "author": "loki-network",
      "body": "<center><a href='https://d.tube/#!/v/loki-network/n9l3w61s'><img src='https://ipfs.io/ipfs/Qma3bg5caUeNkLMWcMXrYcd7w1YMnfj5wL2qUWrxyLZCy4'></a></center><hr>\n\n_________________________________________________________________\nWEBSITE      https://loki.network\nREDDIT         https://www.reddit.com/r/LokiProject/\nTWITTER      https://twitter.com/loki_project\nBTC               https://bitcointalk.org/index.php?top...\nDISCORD      https://discordapp.com/invite/67GXfD6\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TV...\n\n<hr><a href='https://d.tube/#!/v/loki-network/n9l3w61s'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmcD1y8NiPWC9t15tYdyzvtxPBGaJ6BpHduFJKycethDYt'> ▶️ IPFS</a>",
      "json_metadata": "{\"video\":{\"info\":{\"title\":\"Are ASICS A Good Thing?\",\"snaphash\":\"QmYSX1DmxskrDpzQvEXnFXwDL22Q1uizydpZjqKoHkFQZm\",\"author\":\"loki-network\",\"permlink\":\"n9l3w61s\",\"duration\":224.444082,\"filesize\":21608557,\"spritehash\":\"QmaMWidN557Bue2MDdTd7LZbbvjQDK3Ru7Hrks9u3iEW4x\"},\"content\":{\"videohash\":\"QmcD1y8NiPWC9t15tYdyzvtxPBGaJ6BpHduFJKycethDYt\",\"description\":\"_________________________________________________________________\\nWEBSITE      https://loki.network\\nREDDIT         https://www.reddit.com/r/LokiProject/\\nTWITTER      https://twitter.com/loki_project\\nBTC               https://bitcointalk.org/index.php?top...\\nDISCORD      https://discordapp.com/invite/67GXfD6\\nTELEGRAM  https://t.me/joinchat/DeNvR0JJ4JPn6TV...\",\"tags\":[\"loki\",\"fpga\",\"asic\",\"centralization\"],\"video240hash\":\"QmTfRQL4tNFTk1xcHHr1sVu28T2VPb7dxszE1zaxK12S6H\",\"video480hash\":\"QmQiqH9K8b78H8b4VEeCtXScCYqteTN3khmCvxb9cCx6tc\"}},\"tags\":[\"loki\",\"fpga\",\"asic\",\"centralization\",\"dtube\"],\"app\":\"dtube/0.7\"}",
      "parent_author": "",
      "parent_permlink": "loki",
      "permlink": "n9l3w61s",
      "title": "Are ASICS A Good Thing?"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:28:57",
  "trx_id": "203d22df7f32c269c29e40af9bb9f4d02e2e91c2",
  "trx_in_block": 1,
  "virtual_op": 0
}
2018/07/24 14:24:03
authorloki-network
permlinkwn621k7m
votertapash0507
weight100 (1.00%)
Transaction InfoBlock #24458516/Trx fd954d1e9bdc5cd113108f5d8316035ddfa0c7ab
View Raw JSON Data
{
  "block": 24458516,
  "op": [
    "vote",
    {
      "author": "loki-network",
      "permlink": "wn621k7m",
      "voter": "tapash0507",
      "weight": 100
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:24:03",
  "trx_id": "fd954d1e9bdc5cd113108f5d8316035ddfa0c7ab",
  "trx_in_block": 12,
  "virtual_op": 0
}
loki-networkupdated options for wn621k7m
2018/07/24 14:23:09
allow curation rewardstrue
allow votestrue
authorloki-network
extensions[[0,{"beneficiaries":[{"account":"dtube","weight":2500}]}]]
max accepted payout1000000.000 SBD
percent steem dollars10000
permlinkwn621k7m
Transaction InfoBlock #24458498/Trx 779ff6cfa706390d17e4cd5399de32510133034f
View Raw JSON Data
{
  "block": 24458498,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "loki-network",
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "dtube",
                "weight": 2500
              }
            ]
          }
        ]
      ],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "permlink": "wn621k7m"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-07-24T14:23:09",
  "trx_id": "779ff6cfa706390d17e4cd5399de32510133034f",
  "trx_in_block": 24,
  "virtual_op": 0
}

Account Metadata

POSTING JSON METADATA
profile{"profile_image":"https://yt3.ggpht.com/-2pN4Muif4ck/AAAAAAAAAAI/AAAAAAAAABE/R9xqMkDiBTE/s288-mo-c-c0xffffffff-rj-k-no/photo.jpg","name":"Loki Network","about":"Private transactions, decentralised communication.","website":"https://loki.network/","cover_image":"https://yt3.ggpht.com/TX11_sqtQTjzVHwf_k8_xLThTUjmr-d7LpIubY0WvqsQrto5R614STkeO3oKSvoqyc6OuGz0iec=w2120-fcrop64=1,00000000ffffffff-nd-c0xffffffff-rj-k-no"}
JSON METADATA
profile{"profile_image":"https://yt3.ggpht.com/-2pN4Muif4ck/AAAAAAAAAAI/AAAAAAAAABE/R9xqMkDiBTE/s288-mo-c-c0xffffffff-rj-k-no/photo.jpg","name":"Loki Network","about":"Private transactions, decentralised communication.","website":"https://loki.network/","cover_image":"https://yt3.ggpht.com/TX11_sqtQTjzVHwf_k8_xLThTUjmr-d7LpIubY0WvqsQrto5R614STkeO3oKSvoqyc6OuGz0iec=w2120-fcrop64=1,00000000ffffffff-nd-c0xffffffff-rj-k-no"}
{
  "posting_json_metadata": {
    "profile": {
      "profile_image": "https://yt3.ggpht.com/-2pN4Muif4ck/AAAAAAAAAAI/AAAAAAAAABE/R9xqMkDiBTE/s288-mo-c-c0xffffffff-rj-k-no/photo.jpg",
      "name": "Loki Network",
      "about": "Private transactions, decentralised communication.",
      "website": "https://loki.network/",
      "cover_image": "https://yt3.ggpht.com/TX11_sqtQTjzVHwf_k8_xLThTUjmr-d7LpIubY0WvqsQrto5R614STkeO3oKSvoqyc6OuGz0iec=w2120-fcrop64=1,00000000ffffffff-nd-c0xffffffff-rj-k-no"
    }
  },
  "json_metadata": {
    "profile": {
      "profile_image": "https://yt3.ggpht.com/-2pN4Muif4ck/AAAAAAAAAAI/AAAAAAAAABE/R9xqMkDiBTE/s288-mo-c-c0xffffffff-rj-k-no/photo.jpg",
      "name": "Loki Network",
      "about": "Private transactions, decentralised communication.",
      "website": "https://loki.network/",
      "cover_image": "https://yt3.ggpht.com/TX11_sqtQTjzVHwf_k8_xLThTUjmr-d7LpIubY0WvqsQrto5R614STkeO3oKSvoqyc6OuGz0iec=w2120-fcrop64=1,00000000ffffffff-nd-c0xffffffff-rj-k-no"
    }
  }
}

Auth Keys

Owner
Single Signature
Public Keys
STM8XNZwKp424WE9PavYoM4xNVxGYEgbzyf6ttHUGufzvm6AxvZsy1/1
Active
Single Signature
Public Keys
STM7cJeidzu9YSoeRzFM4m4ifiwMz9Ex3XUXia8ca8auz1MnZn78i1/1
Posting
Single Signature
Public Keys
STM7RZBhdS6p5Py8poTqcSeqh6mMqWQRaGFBdvCpFKyfZVEfPjaCK1/1
App Permissions
Memo
STM8aQmxhSha2T7zGrgLEcUdiXT1Qcwp7SwSo8jHkjdQZA5tZ5Mxw
{
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM8XNZwKp424WE9PavYoM4xNVxGYEgbzyf6ttHUGufzvm6AxvZsy",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM7cJeidzu9YSoeRzFM4m4ifiwMz9Ex3XUXia8ca8auz1MnZn78i",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting": {
    "account_auths": [
      [
        "dtube.app",
        1
      ]
    ],
    "key_auths": [
      [
        "STM7RZBhdS6p5Py8poTqcSeqh6mMqWQRaGFBdvCpFKyfZVEfPjaCK",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "memo": "STM8aQmxhSha2T7zGrgLEcUdiXT1Qcwp7SwSo8jHkjdQZA5tZ5Mxw"
}

Witness Votes

0 / 30
No active witness votes.
[]