You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the altruism service works by relaying the fallback calls to a special set of Pocket nodes. These nodes, run by PNI, are out of date and only used for altruism. The feature they use to do this is not supported in future versions and it is an inefficient relay system by all measures.
The altruistic node service should be replaced with service that directly calls the PNF hosted blockchain nodes in US-East-2.
There is an internal ALB that is used for node communication located in US-East-2.
The portal API should keep a stored list of the chain's full URL for use in the backup service.
That stored list could be a GitHub secret that is loaded into an env variable and parsed or the backup location could be stored in the mongo DB as part of the blockchain record.
The text was updated successfully, but these errors were encountered:
Currently the altruism service works by relaying the fallback calls to a special set of Pocket nodes. These nodes, run by PNI, are out of date and only used for altruism. The feature they use to do this is not supported in future versions and it is an inefficient relay system by all measures.
The altruistic node service should be replaced with service that directly calls the PNF hosted blockchain nodes in US-East-2.
There is an internal ALB that is used for node communication located in US-East-2.
All VPCs where the Portal API exists should be VPC peered with the node-infra-manual VPC in US-East-2: https://aws.amazon.com/premiumsupport/knowledge-center/elb-access-load-balancer-vpc-peering/
The portal API should keep a stored list of the chain's full URL for use in the backup service.
That stored list could be a GitHub secret that is loaded into an env variable and parsed or the backup location could be stored in the mongo DB as part of the blockchain record.
The text was updated successfully, but these errors were encountered: