Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.379USD
STEEM
0.000STEEM
SBD
0.000SBD
Own SP
7.027SP

Detailed Balance

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

Account Info

nameatomium
id47946
rank170,561
reputation84569805
created2016-08-06T14:00:15
recovery_accountsteem
proxyNone
post_count1
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2016-08-06T17:24:33
last_root_post2016-08-06T17:24:33
last_vote_time2016-08-08T14:08:03
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power9,851
delayed_votes0
balance0.000 STEEM
savings_balance0.000 STEEM
sbd_balance0.000 SBD
savings_sbd_balance0.000 SBD
vesting_shares11443.011268 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares0.000000 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update1970-01-01T00:00:00
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 47946,
  "name": "atomium",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM65bL2LEmEmJkSTWssWornhHB3emi5WCEiXPqTuVRMaNdwiY91t",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM56VTax34ZFsUVL9PfMZEpLBaw59PQMd1CSXPfmAZ1uxznJJxBY",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM89ziCAuffZwvyDS48KeMGwMNMek1fLezDqGMFPc7p2UTnbUKKm",
        1
      ]
    ]
  },
  "memo_key": "STM68Zx2ZbZVLrHbuL6crnMMJZCQtJPJyTGDAQmDZ9JqsRwukvEPa",
  "json_metadata": "",
  "posting_json_metadata": "",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "created": "2016-08-06T14:00:15",
  "mined": false,
  "recovery_account": "steem",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 1,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": 9851,
    "last_update_time": 1470665283
  },
  "downvote_manabar": {
    "current_mana": 0,
    "last_update_time": 1470492015
  },
  "voting_power": 9851,
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.000 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "1970-01-01T00:00:00",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "0.000 STEEM",
  "reward_vesting_balance": "0.000000 VESTS",
  "reward_vesting_steem": "0.000 STEEM",
  "vesting_shares": "11443.011268 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 0,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2016-08-06T17:24:33",
  "last_root_post": "2016-08-06T17:24:33",
  "last_vote_time": "2016-08-08T14:08:03",
  "post_bandwidth": 10000,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": 84569805,
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 170561
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
2019/08/06 15:11:51
parent authoratomium
parent permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
authorsteemitboard
permlinksteemitboard-notify-atomium-20190806t151150000z
title
bodyCongratulations @atomium! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@atomium/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@atomium) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=atomium)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #35319104/Trx ae939a1fe038596f3ea4f490d853621ce665acca
View Raw JSON Data
{
  "trx_id": "ae939a1fe038596f3ea4f490d853621ce665acca",
  "block": 35319104,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-06T15:11:51",
  "op": [
    "comment",
    {
      "parent_author": "atomium",
      "parent_permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-atomium-20190806t151150000z",
      "title": "",
      "body": "Congratulations @atomium! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@atomium/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@atomium) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=atomium)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
2017/08/08 17:01:42
parent authoratomium
parent permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
authorexrecroter
permlinkre-atomium-how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken-20170808t170214279z
title
bodyGood article
json metadata{"tags":["introduceyourself"],"app":"steemit/0.1"}
Transaction InfoBlock #14400393/Trx cee2ceb1a1a67d81f1412985eb76a9333c1a875f
View Raw JSON Data
{
  "trx_id": "cee2ceb1a1a67d81f1412985eb76a9333c1a875f",
  "block": 14400393,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-08-08T17:01:42",
  "op": [
    "comment",
    {
      "parent_author": "atomium",
      "parent_permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "author": "exrecroter",
      "permlink": "re-atomium-how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken-20170808t170214279z",
      "title": "",
      "body": "Good article",
      "json_metadata": "{\"tags\":[\"introduceyourself\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2016/08/08 14:08:03
voteratomium
authorsharonekelly
permlinkthis-book-is-a-game-changer-for-some-steemiters-period
weight10000 (100.00%)
Transaction InfoBlock #3904667/Trx e563e2986fe0751a054055dd2d0eb91cf31751a5
View Raw JSON Data
{
  "trx_id": "e563e2986fe0751a054055dd2d0eb91cf31751a5",
  "block": 3904667,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-08T14:08:03",
  "op": [
    "vote",
    {
      "voter": "atomium",
      "author": "sharonekelly",
      "permlink": "this-book-is-a-game-changer-for-some-steemiters-period",
      "weight": 10000
    }
  ]
}
2016/08/08 14:05:57
voteratomium
authorholabebe
permlinkdecentralized-amazon-cloud-is-call-storj-share
weight10000 (100.00%)
Transaction InfoBlock #3904626/Trx 43a95a76ebf82f95ebd85488cd6db264a92e2584
View Raw JSON Data
{
  "trx_id": "43a95a76ebf82f95ebd85488cd6db264a92e2584",
  "block": 3904626,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-08T14:05:57",
  "op": [
    "vote",
    {
      "voter": "atomium",
      "author": "holabebe",
      "permlink": "decentralized-amazon-cloud-is-call-storj-share",
      "weight": 10000
    }
  ]
}
2016/08/08 14:05:36
voteratomium
authorholabebe
permlinkpurple-lamborghini-best-video-of-the-year
weight10000 (100.00%)
Transaction InfoBlock #3904620/Trx 3a5abbe06f1e8476c94f326771f6ab9f313b1d0e
View Raw JSON Data
{
  "trx_id": "3a5abbe06f1e8476c94f326771f6ab9f313b1d0e",
  "block": 3904620,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-08T14:05:36",
  "op": [
    "vote",
    {
      "voter": "atomium",
      "author": "holabebe",
      "permlink": "purple-lamborghini-best-video-of-the-year",
      "weight": 10000
    }
  ]
}
2016/08/07 03:36:15
votersharonekelly
authoratomium
permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
weight10000 (100.00%)
Transaction InfoBlock #3863463/Trx 59a11e53396d99e6c5b0c08e036f23cbf6d1d535
View Raw JSON Data
{
  "trx_id": "59a11e53396d99e6c5b0c08e036f23cbf6d1d535",
  "block": 3863463,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-07T03:36:15",
  "op": [
    "vote",
    {
      "voter": "sharonekelly",
      "author": "atomium",
      "permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "weight": 10000
    }
  ]
}
2016/08/06 20:40:09
voterabanks1000
authoratomium
permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
weight10000 (100.00%)
Transaction InfoBlock #3855162/Trx 323bda92be70dd92e381dea4d78659a0c81114df
View Raw JSON Data
{
  "trx_id": "323bda92be70dd92e381dea4d78659a0c81114df",
  "block": 3855162,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-06T20:40:09",
  "op": [
    "vote",
    {
      "voter": "abanks1000",
      "author": "atomium",
      "permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "weight": 10000
    }
  ]
}
2016/08/06 18:11:39
voterjoseph.kalu
authoratomium
permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
weight10000 (100.00%)
Transaction InfoBlock #3852202/Trx 4b4406679755f398b1045c094dd844a0a01be994
View Raw JSON Data
{
  "trx_id": "4b4406679755f398b1045c094dd844a0a01be994",
  "block": 3852202,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-06T18:11:39",
  "op": [
    "vote",
    {
      "voter": "joseph.kalu",
      "author": "atomium",
      "permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "weight": 10000
    }
  ]
}
2016/08/06 17:29:27
voterholabebe
authoratomium
permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
weight10000 (100.00%)
Transaction InfoBlock #3851361/Trx 03e87c290a83031b142860f3b87ee98a97c6c12d
View Raw JSON Data
{
  "trx_id": "03e87c290a83031b142860f3b87ee98a97c6c12d",
  "block": 3851361,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-06T17:29:27",
  "op": [
    "vote",
    {
      "voter": "holabebe",
      "author": "atomium",
      "permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "weight": 10000
    }
  ]
}
2016/08/06 17:25:24
voterregex
authoratomium
permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
weight10000 (100.00%)
Transaction InfoBlock #3851280/Trx cd95d19bbc55df7dfe40725a8da18756726439fc
View Raw JSON Data
{
  "trx_id": "cd95d19bbc55df7dfe40725a8da18756726439fc",
  "block": 3851280,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-06T17:25:24",
  "op": [
    "vote",
    {
      "voter": "regex",
      "author": "atomium",
      "permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "weight": 10000
    }
  ]
}
2016/08/06 17:24:33
voteratomium
authoratomium
permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
weight10000 (100.00%)
Transaction InfoBlock #3851263/Trx 9846941c495d2df6c69ab269fc2736c28743a079
View Raw JSON Data
{
  "trx_id": "9846941c495d2df6c69ab269fc2736c28743a079",
  "block": 3851263,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-06T17:24:33",
  "op": [
    "vote",
    {
      "voter": "atomium",
      "author": "atomium",
      "permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "weight": 10000
    }
  ]
}
2016/08/06 17:24:33
parent author
parent permlinkintroduceyourself
authoratomium
permlinkhow-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken
titleHow to keep 87% of your mobile visitors since the password model is broken?
body(https://mobileconnect.io/wp-content/themes/roots-master/assets/img/mobile_connect_logo_purple_fade.png) The user authentication market as we know it is about to change. There’s one digital device in existence that has more users than any other in the market. It’s in use from the rural villages of India to the sprawling metropolis of the world — the mobile phone. Wouldn’t it be great if you could leverage your phone, which basically never leaves your side, to authenticate to and access online services? Now you can, thanks to Mobile Connect. GSMA and Mobile Connect GSMA represents the interests of mobile operators worldwide. There are several working groups under the GSMA advancing different mobile based technologies, best practices and standards. Under the Personal Data Working Group, there’s a program called Mobile Connect. At the core of Mobile Connect, there’s an adapted version of the OpenID Connect protocol with the aim to create a federated and global mobile identity ecosystem. Let’s take that last sentence apart to get more sense into the techno gibberish. Mobile Connect is Global In some parts of the world, the mobile phone is a very basic device. In some other parts, most people will walk their nose pointed firmly towards the ground (and the 5” screen) as they check their latest snaps, Facebook updates, or try to get through to the next level in Clash of Clans. The global aspect of Mobile Connect takes this into account and allows mobile operators to choose the method of user authentication that is appropriate for their subscribers. More basic devices could use a simple SMS based or non-PKI SIM based authentication, whereas more advanced devices could use an app and the fingerprint to authenticate users to online services. The GSMA calls these authenticators. An authenticator is the piece of technology that provides the means for the end user to establish his identity. An authenticator always uses a device that has an MSISDN (that’s the phone number in plain English). This is the first clever bit of Mobile Connect. The MSISDN can be considered as a unique attribute or identifier. Online services connect to an operator Identity Gateway using the standardized Mobile Connect protocol. The Identity Gateway connects to the authentication server. The authentication server takes care of the actual authentication event by sending the authentication request to the authenticator and validating the response. The type of authenticator(s) selected by the operator defines what kind of authentication servers are required. Sometimes the Identity Gateway and the authentication service come from different vendors. The selection of authenticators is a local issue. As the communication between the online service provider and the identity gateway is standardized, it is straightforward to connect online services and identity gateways on a global scale. Mobile Connect is Federated The second clever part of Mobile Connect is in the federation. Federation is a technology (and agreements) that allow users to move between independent domains without re-authentication. In the Mobile Connect concept, it allows a subscriber of an operator in India for example, to log into an online service in the UK. The key to this capability is something called the discovery service. The normal scenario is that the online service provider is connected to the GSMA Discovery Service (and the Identity Gateway). This discovery service provides the login screen for the end user where the phone number will be typed in by the user. Now for the magic part. The discovery service will check the phone number and… erm… discover that it belongs to an India based operator and routes the authentication request to the home operator of the user. The home operator then pushes the authentication request to the user’s mobile device and the user authenticates. Simple. Enabling the Subscriber When the operator decides to deploy Mobile Connect they will first have to build the infrastructure. So they acquire/build an identity gateway and choose appropriate authenticators for their subscribers. Deploying the hub of the solution, the identity gateway can be done the easy or the hard way. The easy way could be for example using GlobalSign Identity Gateway as a managed solution. This can be up and running in two hours after we receive the call. The hard way is to do it in-house and create a development team, try to pass the conformance tests and maintain the in-house solution as the protocol develops and new features are added over time. Then it’s a question of selecting the authenticator(s). The chosen authenticator is dependent on the market situation and what the subscribers can utilize. There are authenticator options that rely on SMS based technologies and won’t require anything extra to be installed to the user’s phone. The next category would be an authenticator that involves an installation of a small SIM based application, but still using SMS based communication. The larger SIM applications, for example PKI based operations, typically require a new SIM card and means that the subscriber has to visit the operator shop to change his SIM card, however they still use SMS for last leg of the journey from the authentication server to the user device. Then we have smartphone app authenticators (SAA). The cost of deploying an authenticator is an important fact to consider. SAA deployment and the simple SMS based authenticators have zero deployment costs for the operator. A non PKI based SIM client costs a handful of SMS messages to deploy. If the user needs to swap the SIM and visit the operator shop, the cost of the deployment will be at the 10–20$ range / user. Level of Assurance (LoA) Depending on the chosen authenticator, the method will be assigned number (1–4) reflecting the Level of Assurance (LoA) of the authenticator. A multi-factor authenticator will get a higher number as they can be considered stronger. Authenticators that can provide proof that someone pressed “ok” on the mobile phone are assigned a lower number. The online service provider can request a certain level of assurance when they want to authenticate the end user. It’s worth noting that at this moment the LoA of the Mobile Connect only describes the strength of the authentication method, not the identity. The strength of the identity relates to the registration process itself and how the subscriber has been verified when he acquired his mobile phone subscription. In some markets, pre-paid subscriptions can be acquired without any kind of identity verification. Post-paid (invoiced) subscriptions in most markets require a thorough identity verification. Mobile Connect has the potential to become a global method of authenticating online users. In the next part of this blog post I will take a look at the benefits of Mobile Connect for end users, service providers and mobile network operators and discuss how to get started with Mobile Connect. We’ll also take a look at edge cases operators need to figure out if they want their Mobile Connect deployment to be successful. To see Mobile Connect in action @atomiumtech
json metadata{"tags":["introduceyourself","steem","mobile","authentication","connect"],"users":["atomiumtech"],"image":["https://mobileconnect.io/wp-content/themes/roots-master/assets/img/mobile_connect_logo_purple_fade.png"]}
Transaction InfoBlock #3851263/Trx 9846941c495d2df6c69ab269fc2736c28743a079
View Raw JSON Data
{
  "trx_id": "9846941c495d2df6c69ab269fc2736c28743a079",
  "block": 3851263,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-06T17:24:33",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "introduceyourself",
      "author": "atomium",
      "permlink": "how-to-keep-87-of-your-mobile-visitors-since-the-password-model-is-broken",
      "title": "How to keep 87% of your mobile visitors since the password model is broken?",
      "body": "(https://mobileconnect.io/wp-content/themes/roots-master/assets/img/mobile_connect_logo_purple_fade.png)\n\nThe user authentication market as we know it is about to change. There’s one digital device in existence that has more users than any other in the market. It’s in use from the rural villages of India to the sprawling metropolis of the world — the mobile phone. Wouldn’t it be great if you could leverage your phone, which basically never leaves your side, to authenticate to and access online services? Now you can, thanks to Mobile Connect.\n\nGSMA and Mobile Connect\n\nGSMA represents the interests of mobile operators worldwide. There are several working groups under the GSMA advancing different mobile based technologies, best practices and standards. Under the Personal Data Working Group, there’s a program called Mobile Connect. At the core of Mobile Connect, there’s an adapted version of the OpenID Connect protocol with the aim to create a federated and global mobile identity ecosystem. Let’s take that last sentence apart to get more sense into the techno gibberish.\n\nMobile Connect is Global\n\nIn some parts of the world, the mobile phone is a very basic device. In some other parts, most people will walk their nose pointed firmly towards the ground (and the 5” screen) as they check their latest snaps, Facebook updates, or try to get through to the next level in Clash of Clans. The global aspect of Mobile Connect takes this into account and allows mobile operators to choose the method of user authentication that is appropriate for their subscribers. More basic devices could use a simple SMS based or non-PKI SIM based authentication, whereas more advanced devices could use an app and the fingerprint to authenticate users to online services.\nThe GSMA calls these authenticators. An authenticator is the piece of technology that provides the means for the end user to establish his identity. An authenticator always uses a device that has an MSISDN (that’s the phone number in plain English). This is the first clever bit of Mobile Connect. The MSISDN can be considered as a unique attribute or identifier.\n\nOnline services connect to an operator Identity Gateway using the standardized Mobile Connect protocol. The Identity Gateway connects to the authentication server. The authentication server takes care of the actual authentication event by sending the authentication request to the authenticator and validating the response. The type of authenticator(s) selected by the operator defines what kind of authentication servers are required. Sometimes the Identity Gateway and the authentication service come from different vendors. The selection of authenticators is a local issue.\n\nAs the communication between the online service provider and the identity gateway is standardized, it is straightforward to connect online services and identity gateways on a global scale.\n\nMobile Connect is Federated\n\nThe second clever part of Mobile Connect is in the federation. Federation is a technology (and agreements) that allow users to move between independent domains without re-authentication. In the Mobile Connect concept, it allows a subscriber of an operator in India for example, to log into an online service in the UK. The key to this capability is something called the discovery service.\nThe normal scenario is that the online service provider is connected to the GSMA Discovery Service (and the Identity Gateway). This discovery service provides the login screen for the end user where the phone number will be typed in by the user. Now for the magic part. The discovery service will check the phone number and… erm… discover that it belongs to an India based operator and routes the authentication request to the home operator of the user. The home operator then pushes the authentication request to the user’s mobile device and the user authenticates. Simple.\n\nEnabling the Subscriber\n\nWhen the operator decides to deploy Mobile Connect they will first have to build the infrastructure. So they acquire/build an identity gateway and choose appropriate authenticators for their subscribers. Deploying the hub of the solution, the identity gateway can be done the easy or the hard way. The easy way could be for example using GlobalSign Identity Gateway as a managed solution. This can be up and running in two hours after we receive the call. The hard way is to do it in-house and create a development team, try to pass the conformance tests and maintain the in-house solution as the protocol develops and new features are added over time.\nThen it’s a question of selecting the authenticator(s). The chosen authenticator is dependent on the market situation and what the subscribers can utilize. There are authenticator options that rely on SMS based technologies and won’t require anything extra to be installed to the user’s phone. The next category would be an authenticator that involves an installation of a small SIM based application, but still using SMS based communication. The larger SIM applications, for example PKI based operations, typically require a new SIM card and means that the subscriber has to visit the operator shop to change his SIM card, however they still use SMS for last leg of the journey from the authentication server to the user device. Then we have smartphone app authenticators (SAA).\nThe cost of deploying an authenticator is an important fact to consider. SAA deployment and the simple SMS based authenticators have zero deployment costs for the operator. A non PKI based SIM client costs a handful of SMS messages to deploy. If the user needs to swap the SIM and visit the operator shop, the cost of the deployment will be at the 10–20$ range / user.\n\nLevel of Assurance (LoA)\n\nDepending on the chosen authenticator, the method will be assigned number (1–4) reflecting the Level of Assurance (LoA) of the authenticator. A multi-factor authenticator will get a higher number as they can be considered stronger. Authenticators that can provide proof that someone pressed “ok” on the mobile phone are assigned a lower number. The online service provider can request a certain level of assurance when they want to authenticate the end user.\nIt’s worth noting that at this moment the LoA of the Mobile Connect only describes the strength of the authentication method, not the identity. The strength of the identity relates to the registration process itself and how the subscriber has been verified when he acquired his mobile phone subscription. In some markets, pre-paid subscriptions can be acquired without any kind of identity verification. Post-paid (invoiced) subscriptions in most markets require a thorough identity verification.\n\nMobile Connect has the potential to become a global method of authenticating online users. In the next part of this blog post I will take a look at the benefits of Mobile Connect for end users, service providers and mobile network operators and discuss how to get started with Mobile Connect. We’ll also take a look at edge cases operators need to figure out if they want their Mobile Connect deployment to be successful.\n\nTo see Mobile Connect in action @atomiumtech",
      "json_metadata": "{\"tags\":[\"introduceyourself\",\"steem\",\"mobile\",\"authentication\",\"connect\"],\"users\":[\"atomiumtech\"],\"image\":[\"https://mobileconnect.io/wp-content/themes/roots-master/assets/img/mobile_connect_logo_purple_fade.png\"]}"
    }
  ]
}
steemcreated a new account: @atomium
2016/08/06 14:00:15
fee3.000 STEEM
creatorsteem
new account nameatomium
owner{"weight_threshold":1,"account_auths":[],"key_auths":[["STM65bL2LEmEmJkSTWssWornhHB3emi5WCEiXPqTuVRMaNdwiY91t",1]]}
active{"weight_threshold":1,"account_auths":[],"key_auths":[["STM56VTax34ZFsUVL9PfMZEpLBaw59PQMd1CSXPfmAZ1uxznJJxBY",1]]}
posting{"weight_threshold":1,"account_auths":[],"key_auths":[["STM89ziCAuffZwvyDS48KeMGwMNMek1fLezDqGMFPc7p2UTnbUKKm",1]]}
memo keySTM68Zx2ZbZVLrHbuL6crnMMJZCQtJPJyTGDAQmDZ9JqsRwukvEPa
json metadata
Transaction InfoBlock #3847183/Trx 979148279bee2637a34084366e614f224cad3ce4
View Raw JSON Data
{
  "trx_id": "979148279bee2637a34084366e614f224cad3ce4",
  "block": 3847183,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2016-08-06T14:00:15",
  "op": [
    "account_create",
    {
      "fee": "3.000 STEEM",
      "creator": "steem",
      "new_account_name": "atomium",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM65bL2LEmEmJkSTWssWornhHB3emi5WCEiXPqTuVRMaNdwiY91t",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM56VTax34ZFsUVL9PfMZEpLBaw59PQMd1CSXPfmAZ1uxznJJxBY",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM89ziCAuffZwvyDS48KeMGwMNMek1fLezDqGMFPc7p2UTnbUKKm",
            1
          ]
        ]
      },
      "memo_key": "STM68Zx2ZbZVLrHbuL6crnMMJZCQtJPJyTGDAQmDZ9JqsRwukvEPa",
      "json_metadata": ""
    }
  ]
}

Account Metadata

POSTING JSON METADATA
None
JSON METADATA
None
{
  "posting_json_metadata": {},
  "json_metadata": {}
}

Auth Keys

Owner
Single Signature
Public Keys
STM65bL2LEmEmJkSTWssWornhHB3emi5WCEiXPqTuVRMaNdwiY91t1/1
Active
Single Signature
Public Keys
STM56VTax34ZFsUVL9PfMZEpLBaw59PQMd1CSXPfmAZ1uxznJJxBY1/1
Posting
Single Signature
Public Keys
STM89ziCAuffZwvyDS48KeMGwMNMek1fLezDqGMFPc7p2UTnbUKKm1/1
Memo
STM68Zx2ZbZVLrHbuL6crnMMJZCQtJPJyTGDAQmDZ9JqsRwukvEPa
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM65bL2LEmEmJkSTWssWornhHB3emi5WCEiXPqTuVRMaNdwiY91t",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM56VTax34ZFsUVL9PfMZEpLBaw59PQMd1CSXPfmAZ1uxznJJxBY",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM89ziCAuffZwvyDS48KeMGwMNMek1fLezDqGMFPc7p2UTnbUKKm",
        1
      ]
    ]
  },
  "memo": "STM68Zx2ZbZVLrHbuL6crnMMJZCQtJPJyTGDAQmDZ9JqsRwukvEPa"
}

Witness Votes

0 / 30
No active witness votes.
[]