Viewing a response to: @zappl/re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t003249874z
First there this ...  Then you said ... > If you look at the tickets we have closed tickets with out commenting ... > # but the fix had still been put in. Ok, so the fix had still been put in. Then you said ... > Ah what your referring to is transaction being handled on the server and not in the browser. So is there a fix currently in GitHub or not?
| author | inertia |
|---|---|
| permlink | re-zappl-re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t004103510z |
| category | zappl |
| json_metadata | {"tags":["zappl"],"image":["https://steemitimages.com/DQmcQhgbUYF88j8tA8RSSs1YDZ6fgFruB583wG4vsNJYYqQ/image.png"],"app":"steemit/0.1"} |
| created | 2018-02-13 00:41:03 |
| last_update | 2018-02-13 00:41:03 |
| depth | 9 |
| children | 5 |
| last_payout | 2018-02-20 00:41:03 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 446 |
| author_reputation | 346,568,901,399,561 |
| root_title | "Let Zappl Clerify some things. FUD Correction" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 37,065,556 |
| net_rshares | 0 |
When I trying using zappl, it so perfectly app So I hope this can fast get solution, I will trying to help if you need
| author | ridhosafwan | ||||||
|---|---|---|---|---|---|---|---|
| permlink | re-inertia-2018214t22144639z | ||||||
| category | zappl | ||||||
| json_metadata | {"tags":"zappl","app":"esteem/1.5.0","format":"markdown+html","community":"esteem"} | ||||||
| created | 2018-02-13 19:21:48 | ||||||
| last_update | 2018-02-13 19:21:48 | ||||||
| depth | 10 | ||||||
| children | 0 | ||||||
| last_payout | 2018-02-20 19:21:48 | ||||||
| cashout_time | 1969-12-31 23:59:59 | ||||||
| total_payout_value | 0.000 HBD | ||||||
| curator_payout_value | 0.000 HBD | ||||||
| pending_payout_value | 0.000 HBD | ||||||
| promoted | 0.000 HBD | ||||||
| body_length | 118 | ||||||
| author_reputation | 113,761,409,575 | ||||||
| root_title | "Let Zappl Clerify some things. FUD Correction" | ||||||
| beneficiaries |
| ||||||
| max_accepted_payout | 1,000,000.000 HBD | ||||||
| percent_hbd | 10,000 | ||||||
| post_id | 37,284,754 | ||||||
| net_rshares | 586,805,086 | ||||||
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| enka.iwan | 0 | 586,805,086 | 100% |
We don't save keys, that data is sent and signed in the server. The connection.js file shows how zappl handles data. That we do save, What your referring to is me talking about the how we handle tickets. We don't capture keys in a database, What we do is sign transaction via the server. Which it appears people don't agree with. We were already aware of this since you brought it up to @thedegensloth in discord before. There is an update to browserfiy transaction for this is already in the works, since before this issue showed up in this posts. Zappl is not capturing your keys and storing them. It is signing transaction via the server though instead of the browser. Which will be corrected since people seem to disagree with the method being used. Please feel free to see how the server handles things here: https://github.com/Zappl/Zappl/tree/master/server
| author | zappl |
|---|---|
| permlink | re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t005916497z |
| category | zappl |
| json_metadata | {"tags":["zappl"],"users":["thedegensloth"],"links":["https://github.com/Zappl/Zappl/tree/master/server"],"app":"steemit/0.1"} |
| created | 2018-02-13 00:59:15 |
| last_update | 2018-02-13 00:59:15 |
| depth | 10 |
| children | 3 |
| last_payout | 2018-02-20 00:59:15 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 869 |
| author_reputation | 41,244,449,218,741 |
| root_title | "Let Zappl Clerify some things. FUD Correction" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 37,068,784 |
| net_rshares | 0 |
[](https://github.com/Zappl/Zappl/blob/master/server/api/index.js#L3039) So, the way I read it, if there's an error broadcasting the transfer, you're writing everything in the POST body to the log files. That would include the wif active key.
| author | inertia |
|---|---|
| permlink | re-zappl-re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t011107600z |
| category | zappl |
| json_metadata | {"tags":["zappl"],"image":["https://steemitimages.com/DQmddcw3uwsLPf7Lpxe5UvKtUvfeQ7ttWpjv3Yof39uEMmx/image.png"],"links":["https://github.com/Zappl/Zappl/blob/master/server/api/index.js#L3039"],"app":"steemit/0.1"} |
| created | 2018-02-13 01:11:06 |
| last_update | 2018-02-13 01:11:06 |
| depth | 11 |
| children | 2 |
| last_payout | 2018-02-20 01:11:06 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 332 |
| author_reputation | 346,568,901,399,561 |
| root_title | "Let Zappl Clerify some things. FUD Correction" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 37,070,960 |
| net_rshares | 0 |
We will exclude the log of keys thank you for letting us know about that. This will be corrected and all log files have been dumped. And the files have been shredded. Just to be public about the log files we dumped there were no keys in the files. But as inertia let us know as the site scales it was possible. Currently zappl load balances so its less likely and error would occur that keys would be caused to be dumped in logs. But zappl will make sure keys even on error don't save in logs. This will be a temp fix until browserfy methods and updated in.
| author | zappl |
|---|---|
| permlink | re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t012330713z |
| category | zappl |
| json_metadata | {"tags":["zappl"],"app":"steemit/0.1"} |
| created | 2018-02-13 01:23:30 |
| last_update | 2018-02-13 01:25:09 |
| depth | 12 |
| children | 1 |
| last_payout | 2018-02-20 01:23:30 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 559 |
| author_reputation | 41,244,449,218,741 |
| root_title | "Let Zappl Clerify some things. FUD Correction" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 37,073,325 |
| net_rshares | 621,948,802 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| indramaulana | 0 | 621,948,802 | 100% |
hiveblocks