Have been attempting to make requests of GigaWallet to generate some invoices for the account 'some_hash' via the following: sudo docker exec -it gigawallet sh -c 'curl -X POST http://localhost:8081/account/some_hash/invoice -H "Content-Type: application/json" -d '\''{ "items": [ { "name": "Dogecoin Sticker", "value": "100.00", "quantity": 1, "type": "item" } ], "required_confirmations": 3 }'\''' unfortunately this neither returns a failure or the expected response, when I look at the logs there is nothing, and when I request a list of invoices for the account by passing: curl --request GET --url ' http://localhost:8081/account/some_hash/invoices?limit=2&cursor=0 ' GigaWallet returns 'null' as a list of items so I can confirm, sadly no invoice has been generated. 😢

georgeartem "value": "100.00" Change to: "value": 100.00 I think it should work :)

hmmm I figured there might be something wrong in the docs when it came to "value": being a string, but unfortunately changing it to a number did not resolve 😢

georgeartem hmmm, strange, try to change the port to 8082 on your command

something is malformed when attempting to generate invoice

georgeartem

that seems very hacky and would pass exactly zero audits.

Inevitable360

georgeartem

There is 2 ports, you can use one as internal/private port and another as a public port

tjstebbing

gigawallet has two web-server ports, one is the 'public api' which is designed for clients that want to pay invoices. the 'admin api' is supposed to be called from your backend systems and is an internal, trusted api that should be behind a firewall.

georgeartem

Okay. I will try it. It would be helpful to highlight which account/invoice end points belong to which service in the documentation. I believe this fact is referenced in only one location which is the gigaconf.toml file example and can easily be forgotten/overlooked by someone who is brand new.

  [WebAPI]
    adminbind = "localhost"  # avoids macOS firewall confirmation!
    adminport = "8081"
    pubbind = "localhost"  # avoids macOS firewall confirmation!
    pubport = "8082"
    pubapirooturl = "http://localhost:8082"

tjstebbing

Yep I'll try to get some more documentation asap :)

georgeartem

simply changing the port to 8082 as suggested returns a 404 - this leads me to believe that you may have an issue with version control as I have suggested in other posts. It would be wise to buckle this down prior to the next release 🙏

H7-25

I've the same issue:
gigawallet@server:~/gigawallet/build$ curl -X POST http://localhost:8081/account/1/invoice -H 'Content-Type: application/json' -d '{ "required_confirmations": 1, "items": [ { "type": "item", "name": "GigaWallet Test", "value": "10.00", "quantity": 1 } ] }' gigawallet@server:~/gigawallet/build$ du -h * 4,0K events.log 18M gigawallet 108K gigawallet.db 4,0K system.log gigawallet@server:~/gigawallet/build$ tail -f system.log 00:44:55.029973 SYS:SYS_STARTUP (577eddb1): ZMQ: connecting to: tcp://192.168.178.50:28332 ^C gigawallet@server:~/gigawallet/build$ tail -f events.log 00:44:55.029974 SYS:SYS_STARTUP (577eddb1): ZMQ: connecting to: tcp://192.168.178.50:28332 00:45:06.775806 ACC:ACC_CREATED (05f166fc): {D8qe8uqnsbRWQ8LasJLHsktEWGSsReD7k5 1 0 } ^C gigawallet@server:~/gigawallet/build$ curl -X GET http://localhost:8081/account/1/invoices {"items":null,"cursor":0}

H7-25

@Inevitable360 can I ask you wich gigawallet version are you using to make it work for shibeship ?
I'm currently testing current main git branch on Debian bookworm . I've try both sqlite and postgresql backend.

Inevitable360

Hello H7-25
I'm currently using the latest main on ShibeShip.com dogecoinfoundation/gigawallettree/main 🙂

H7-25

@Inevitable360 I've found the problem !
`gigawallet@server:~/gigawallet$ curl -X POST http://localhost:8081/account/dogecoinlab/invoice -H 'Content-Type: application/json' -d '{"required_confirmations":1,"items":[{"type":"item","name":"GigaWallet Test","value":"10.00","quantity":1}]}'

gigawallet@server:~/gigawallet$ curl -X POST http://localhost:8081/account/dogecoinlab/invoice/ -H 'Content-Type: application/json' -d '{"required_confirmations":1,"items":[{"type":"item","name":"GigaWallet Test","value":"10.00","quantity":1}]}'
{"id":"DRzLr3xhAYjKwRjE6fRJTSRKY2nHgNzJF2","items":[{"type":"item","name":"GigaWallet Test","sku":"","description":"","value":"10","quantity":1,"image_link":""}],"created":"2024-02-15T19:50:12.262241281+01:00","total":"10","pay_to_address":"DRzLr3xhAYjKwRjE6fRJTSRKY2nHgNzJF2","required_confirmations":1,"part_payment_detected":false,"total_payment_detected":true,"total_payment_confirmed":false,"payment_unconfirmed":false,"estimate_seconds_to_confirm":0}gigawallet@server:~/gigawallet$`

It seems the api url need the final slash form some stuff !

georgeartem

H7-25 cool thank you, going to try this out 🙏

H7-25

georgeartem fixed 😀 dogecoinfoundation/gigawallet4daef70

Inevitable360

Much wow 😁