-
Notifications
You must be signed in to change notification settings - Fork 17
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
Typescript Doc #15
Comments
It requires a complete node to be run. Without a verge node, you won't be able to request anything. How to init it: How to (for example) get transaction lists: Supported Methods: (it's WIP) |
To your other question about to send XVG to multiple addresses: It's not yet supported. |
I've a full node running on my system. It's 100% synced too. I've added verge.config file in %appdata% folder. I have entered proper user and pass values in my node application. Still am not able to fetch the data. |
Then it should work if you have done everything correctly, which it sounds. Show me the config & the code for the connection otherwise, I can't help you right now. |
verge.conf (I've created it in VERGE folder in %appdata%. Its not a .txt file. I've checked it properly)
In node cli Inside node's app.js file
When I execute this, it throws error that .auth isn't a function. |
If I do this It starts throwing error. 'node-verge' module not found. |
This:
Should be this:
And please make sure your verge node is running on the same system (meaning localhost)! |
I'm using above code and trying to call getInfo method.
It's giving me following error: Yes, my Verge wallet is synced fully and is on same machine where am running my node application. |
Still its not working. |
I've installed verge-node
npm install verge-node-typescript;
I've imported it in my node project
var verge = require(verge-node-typescript);
When I try to execute the code in the document, I start getting error message that its not a function.
And it doesn't throw any error or result.
Kindly write document for using it.
Thank you ..
The text was updated successfully, but these errors were encountered: