Viewing a response to: @zappl/re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t000617578z
hiveblocksIs this commit (`f83e31`) active on zappl.com? It contains the code I'm talking about in Issue #5:
```javascript
data = {
token: token,
activeWif: transferActiveWif,
to: transferTo,
amount: transferAmount
}
```
Which submits the wif to a zappl api.
```javascript
this.postWithdrawSteem = function(data){
var response = $http.post("/api/postWithdrawSteem", data);
return response;
}
```| author | inertia |
|---|---|
| permlink | re-zappl-re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t001726426z |
| category | zappl |
| json_metadata | {"tags":["zappl"],"app":"steemit/0.1"} |
| created | 2018-02-13 00:17:27 |
| last_update | 2018-02-13 00:31:42 |
| depth | 7 |
| children | 8 |
| last_payout | 2018-02-20 00:17:27 |
| 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 | 401 |
| 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,061,367 |
| net_rshares | 0 |
Ah what your referring to is transaction being handled on the server and not in the browser. So i would assume everyone just wants transaction processed via the browser on everything? These are the only thing that are handled by a db: https://github.com/Zappl/Zappl/blob/f83e3130b005008317e73748da82b08fb01c0204/server/db/connect.js
| author | zappl |
|---|---|
| permlink | re-inertia-re-zappl-re-inertia-re-zappl-re-inertia-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t003249874z |
| category | zappl |
| json_metadata | {"tags":["zappl"],"links":["https://github.com/Zappl/Zappl/blob/f83e3130b005008317e73748da82b08fb01c0204/server/db/connect.js"],"app":"steemit/0.1"} |
| created | 2018-02-13 00:32:51 |
| last_update | 2018-02-13 00:32:51 |
| depth | 8 |
| children | 7 |
| last_payout | 2018-02-20 00:32:51 |
| 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 | 334 |
| 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,064,141 |
| net_rshares | 0 |
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 |
ok
| author | zan-zhu-zeng | ||||||
|---|---|---|---|---|---|---|---|
| permlink | re-zappl-2018214t103924310z | ||||||
| category | zappl | ||||||
| json_metadata | {"tags":["zappl"],"app":"esteem/1.5.1","format":"markdown+html","community":"esteem"} | ||||||
| created | 2018-02-14 03:39:30 | ||||||
| last_update | 2018-02-14 03:39:30 | ||||||
| depth | 9 | ||||||
| children | 0 | ||||||
| last_payout | 2018-02-21 03:39: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 | 2 | ||||||
| author_reputation | 105,719,718,834 | ||||||
| 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,372,559 | ||||||
| net_rshares | 0 |