Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node-1 not services obscuronscan API endpoints #867

Open
moraygrieve opened this issue Nov 23, 2022 · 0 comments
Open

Node-1 not services obscuronscan API endpoints #867

moraygrieve opened this issue Nov 23, 2022 · 0 comments

Comments

@moraygrieve
Copy link
Contributor

See summary at https://discord.com/channels/916052669955727371/945360340613484684/1044899720549642320, and as below;

It's deploying fine AFAIS, ERC20 contracts are deployed, and I am able to run 95% of my tests successfully against it. 
In all my tests the wallet extension is configured against dev-testnet.obscu.ro and port 13000, and I transact through that. 
Even though I am transacting I don't see any logging in datadog for any particular transaction hashes which is odd. If I use 
the same node details to request total or latest transactions via the obscuroscan_* endpoints it returns zero or nil. If I try 
and get the rollup for a transaction that I received a transaction receipt from, it tells me no rollup contains that transaction.

dev-testnet.obscu.ro  actually routes to node-1 which is dev-obscuronode-1-testnet-112.uksouth.cloudapp.azure.com and
 is the validator node.  If instead of going to dev-testnet.obscu.ro to hit the obascuroscan_ endpoints we go to node-0 at 
dev-obscuronode-0-testnet-112.uksouth.cloudapp.azure.com which is the aggregator node we see the transactions. So it 
seems somehow node-1 is not responding as we expect to requests on these endpoints. Is this fair?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant