Skip to content

Security at Pog.Network

Threat Model



  • gRPC

  • gRPC Requests are the requests made by the client to the node. Requests can range from fetching the wallet balance to updating the node.

  • gRPC Responses are the node's responses that provide the requested necessary information to the client.

  • Database

Database queries, in the diagram marked as data exchanges, handle saving and retrieving the data for the services and the node.


  • All outgoing connections

Description These include the P2P Networking and gRPC connections between the node and the Web Clients.

DDOS: We plan to add rate limiting and, we will guide Node Operators for optimal setup as we won't run the nodes ourselves.
(Denial of Service, High Severity)

Insecure SSL version: In a release, we plan to refuse connections with a TLS version different than 1.3 and refuse insecure connections. Currently, everything is accepted for development purposes.
(Tamperling, High Severity)

  • All Web Clients

Description These include the Wallet and the Admin interfaces.

XSS Attacks: Mitigated because React sanitizes all user input and therefore prevents accidental script injections. Furthermore, we plan to implement a Content Security Policy.
(Elevation of Privilege, High Severity)

  • Node Admin and Node Wallet Manager Web Clients only

CSRF Attacks: Mitigated because we avoid using Cookies that could carry sensitive information. Our short-lived JWTs are stored in the browser session storage.
(Spoofing, High Severity)

  • Node Admin Service and Node Wallet Manager Service

Description: These Services are the endpoints for the Web Clients of similar name. The severtiy of these attacks are lower, as these enpoints are not open to the internet by default but are contained within the local network.

Credential Stuffing: Mitigated because we hash passwords in storage and we use the Have I Been Pwned Range API to securely (with k-Anonymity) check if a password has been part of a breach.
(Elevation of Privilege, Medium Severity)

Credential Cracking: Mitigated because we hash passwords that take longer to compare and we plan to implement a rate limiting mechanism.
(Elevation of Privilege, High Severity)

  • Wallet and Public API

Description: This is the endpoint to the Wallet Web Client that handels user requests to view their wallet or chain information.

High Complexity Queries: We plan to add size limits to requests to preventing users from executing high workload requests.
(Denial of Service, Medium Severity)

Credential Cracking: Mitigated because the attacker will need to have access to the Wallet file that should never leave the users PC. If the attacker has access to the Wallet file on the PC, the attacker would also be able to install a password logger.
(Elevation of Privilege, Low Severity)

  • Database

Injection: Mitigated because we use the Sled database that works more as a key-value storage and is therefore not susceptible to injection. Also, the data is serialized with protobuf.
(Elevation of Privilege, High Severity)

  • Peer to Peer

DDOS: We plan to add rate limiting and we will guide Node Operators for optimal setup as we won't run the Nodes ourselves.
(Denial of Service, High Severity)

Sybil: Mitigated because our consensus algorithm prioritizes accounts that lose money over a period of time which makes farmed account importance inconsistant. We also plan to polish this algorithm and create another that attempts to recognize farming accounts.
(Sybil, High Severity)

Block Gap Sync: We plan to have Nodes wait until the Prime Delegates have voted. If they decide that the block is fraudulent, it can be ignored. Otherwise the Node with the gap in previous block will sync its chain with a Prime Delegate Node.
(Denial of Service, Low Severity)

Penny-spend Attack: Mitigated because we rate-limit transactions in a block. We also decrease an account importance when it starts spamming. In addition, we plan to add a way for Prime Delegates to remove accounts with low importance that act maliciously.
(Ledger bloat, Medium Severity)

>50% Attack: Mitigated because the consensus algorithm favours the Wallets that are active in the network. These Wallets would not benefit from devaluing the coins.
(Destructive, High Severity)

New-user DDOS: We plan to have chain syncing that needs confirmation from multiple Prime Delegates that ensure the validity of the chains sent.
(Denial of Service, Low Severity)


  • Alexander Gemmingen (@Alyks1)
  • Have I been pwned API check [1]
  • Crypto module (such as block signing and JWT) (Pair-Programming with Henry Gressmann) [1] [2]
  • Designed graphs & calculations for the consensus algorithm [1] [2]