Discussion of ActorForth and related projects under the ActorForth organization.
I can share my seed with you, it has few cents so you can test
Instead of /address/utxo it should be /v2/address/utxo like https://rest.bch.actorforth.org/v2/address/utxo
If you try it out using the interface explorer at https://rest.bch.actorforth.org/#/address/utxoBulk you should be able to create a successful call.
It works from the browser but not from python
Hi all and @scherrey (directed me from Telegram): quick question -- I'm using ECASH SLP 3.7.0-beta on windows and just tried to create a token. (options: qty=3, Fixed Supply = FALSE, Is NFT Parent? = TRUE). When I try, I get error 'node' with title ? and yellow exclamation point. NB: Had no problem sending BCH to this wallet and green circle indicating liveness correctly appears in bottom right hand. Would love any help I can get in troubleshooting-- sorry I'm just beginning here.
@anirudhab we think we may have found your issue. Will have more information shortly.
@anirudhab we've made a new build. See if this doesn't fix your problem. https://github.com/ActorForth/ECash-SLPDB/releases/tag/3.7.1
You might be interested int his : https://read.cash/@ClearSky/create-slp-transactions-in-python-using-electron-cash-slp-cli-61f12d65
1 reply
So I have done something dumb, but before I explain it, is there a wallet that can be used for handling thousands of addresses and SLP tokens. EC-SLP (currently using ECash-SLPDB-3.7.1-gb78d52567 from Actorforth) happily let me make and transfer small amounts to some thousands of addresses, but whenever I try to assemble a transfer out of the wallet, it soft locks for hours and hours and sometimes the gui will show the calculated max send amount, but I can never send it. Additionally, this particular setup is showing me some very strange in wallet behaviour such as invalid SLP transactions that when viewed on the blockchain they are fine.
Also, hello gentlemen and otherwise of Actorforth
Also as you guys have seemed to start building EC-SLP (Great job on the most recent release. Big improvement.) I discovered an issue that is related to what I previously mentioned and was wondering if is possible it is fixed in your releases.
That would be this: simpleledger/Electron-Cash-SLP#209 which is related to this feature: simpleledger/Electron-Cash-SLP#93
Ok so I have a small update based on the EC devs, in situations such as myself, the MAX button will never finish and even if it does, it will create a transaction too large to broadcast. They recommended using the "Coins" tab and try to spend from a select amount of addresses, 600 max by selecting them, right clicking and spend. When doing so, there is another MAX button that appears and logically pressing the MAX button while having selected specific inputs should calculate the MAX for those particular inputs/coins. It does not, it tries again to calculate the entire MAX send for the entire wallet. EC devs mentioned in regular EC, the behavior is to only calculate the MAX for the selected coins but they were uncertain about SLP edition. I am confirming SLP wrongly calculates the entire wallet instead of just the selected coins.
@nicolaiskye: Small but important update above
Thank you for your update. I've opened this now as an issue on our Github page for ECash SLPDB so our team can better track it. I'll be sure to let you know if we push any new updates to the wallet.
1 reply
I tried to run slpvalidate on the specific transaction from the console but this doesnt seem to do or fix anything
"Invalid: insufficient valid inputs" is the return.
Happy to work with someone an send/show them transaction ids
I'm continuing to work on this and try to narrow down exactly what is going on with it, it seems very random when they fail and rebuilding wallet history seems to randomly show different failed SLP validation ids.
Same wallet (opened locally (windows) + remotely (linux), different fails for different SLP transactions, randomly
Going to also run 3.6.6. version to see if I can get the same behavior, cannot remember if it ALSO does that
Hey @scherrey yes there are some reports on the EC-SLP github regarding this issue as well. The problem seems to be expounded as well by a poor quality internet connection. I am able to test on both a co-located dedicated server with dedicated internet, which does encounter this issue (but slightly less so), in this case the issue stems LIKELY from the index server load , and locally from my poor quality internet which happens more often. I'm still learning and digging through code (Python noob) and trying to figure out how to force a transaction to revalidate instead of rebuilding from history. The revalidate_slp command, doesn't actually seem to work and further complication, SLP transactions that are invalid are excluded from coinselection which essentially orphans those UTXOs on the wallet.
ahem read
ActorForth is a project group but I presume you mean our rest apis supporting BCH. https://rest.bch.actorforth.org is a fully compatible https API with the original rest.bitcoin.com apis which have announced they're being shut down. FullStack.cash provides functional apis as an alternative but they have different syntax so are not compatible directly. To move from rest.bitcoin.com to rest.bch.actorforth.org all you need to do is change the host name and everything else should just work. To migrate to FullStack.cash you'll have to change the hostname as well as the API calls and your code base for your BCH app to continue functioning.
@prashantpawar FYI