Qortal Project

The future of blockchain platforms

User Tools

Site Tools


browser_trading_security_risk

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
browser_trading_security_risk [03/17/2021 02:17] – created gfactorbrowser_trading_security_risk [02/03/2022 03:57] (current) gfactor
Line 1: Line 1:
 ====== Browser Trading Security Risk ====== ====== Browser Trading Security Risk ======
 +{{:qortal_official_logo_transparent_.png?400|}}
  
-When accessing Qortal's UI by Crowetic's (http://node21.qortal.org:12388) or anyone else'community node, it is NOT recommended to tradeIt seems that the Trade Portal info did not generate when we tested this service out in the browser while accessing the UI through Crowetic's community node, but a trade was still able to be listed on chainThe only data This is why the core limits you to using localhost to issue trades. +The risk is that a bad actor could setup a community node and steal coin keysThe trade bot has to have the keys in order to issue the transactions on your account'behalf, so that means the community node you are accessing would have your keys. This is why the core limits you to using localhost to issue trades
 + 
 +The best advice is to set up your own node and have complete control over your node! There’s no reason to access Qortal on any other device than what you directly control
browser_trading_security_risk.1615961824.txt.gz · Last modified: 03/17/2021 02:17 by gfactor