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
Hello there,
thanks for your support to IOTA community. Your visualizer is very cool and that's the reason why I want to use with my private Tangle and use it for research purposes.
However, how is stated on the title, I've problem when I specify custom LSM and ZMQ endpoints pointing to my local IRI node and Coordinator: the application starts normally and receives all the milestones as well as it does complete the connection with IRI node; however, when I access the website, there are always the same mocked transactions as it can be seen from index.html file. Can you provide the version that is online on your website http://tangle.glumb.de/ so that we can use it locally?
I appreciate any help: it is important for the sake of research to visualize how the Tangle is evolving in specific use-cases, to better justifying the validity of the solution.
Best,
Andrea
The text was updated successfully, but these errors were encountered:
Hello there,
thanks for your support to IOTA community. Your visualizer is very cool and that's the reason why I want to use with my private Tangle and use it for research purposes.
However, how is stated on the title, I've problem when I specify custom LSM and ZMQ endpoints pointing to my local IRI node and Coordinator: the application starts normally and receives all the milestones as well as it does complete the connection with IRI node; however, when I access the website, there are always the same mocked transactions as it can be seen from index.html file. Can you provide the version that is online on your website http://tangle.glumb.de/ so that we can use it locally?
I appreciate any help: it is important for the sake of research to visualize how the Tangle is evolving in specific use-cases, to better justifying the validity of the solution.
Best,
Andrea
The text was updated successfully, but these errors were encountered: