Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 12 09:53
    siraben commented #1
  • Jun 12 09:53
    siraben commented #1
  • May 26 06:44
    scherrey commented #23
  • May 23 17:10
    Sameeranjoshi commented #23
  • May 21 12:37

    scherrey on filepos

    Updated refdocs. (compare)

  • May 20 10:11

    scherrey on filepos

    Added compiling to categories a… Merge branch 'filepos' of githu… (compare)

  • May 12 07:34
    Sameeranjoshi commented #23
  • May 12 07:16
    scherrey commented #23
  • May 12 07:16
    scherrey commented #23
  • May 12 05:33
    Sameeranjoshi commented #23
  • May 12 05:32
    Sameeranjoshi commented #23
  • May 09 17:06

    scherrey on filepos

    Add initial Makefile. Uncomment… Improve parallel builds. Improve parallel builds. and 7 more (compare)

  • May 08 13:51
    MayaPosch commented #23
  • May 08 13:45

    MayaPosch on master

    Separate unit tests into separa… (compare)

  • May 08 09:56
    scherrey closed #17
  • May 08 09:56
    scherrey commented #17
  • May 08 09:54
    scherrey assigned #23
  • May 08 09:54
    scherrey opened #23
  • Apr 28 11:58

    scherrey on filepos

    temporarily added commercial.md… (compare)

  • Apr 26 15:16

    MayaPosch on master

    Exclude perf on Windows. Fix co… (compare)

Damascene
@uak_gitlab
I'm just adding your rest api to this https://mint.bitcoin.com/#/configure
I can share my seed with you, it has few cents so you can test
Damascene
@uak_gitlab
in a separate subject I would like to request two endpoints. 1. total_received_token to get the total of specific token received on an address and total_sent_token.
Ben Scherrey
@scherrey
Which specific https request were you hitting when you got the 404s?
Ben Scherrey
@scherrey
@uak_gitlab I think I see your requests cause I see a lot of 404 responses. Looks like you're missing the /v2/ at the beginning of your path.
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.
Damascene
@uak_gitlab
@scherrey I guess you have some protection on the server that is preventing the call from python without proper headers
It works from the browser but not from python
Damascene
@uak_gitlab
I think I figured it out. I was requesting using double slash // bitcoin.com was ok with it
Damascene
@uak_gitlab
But couldn't make it work on mint.bitcoin.com, could be an issue on their side
Ben Scherrey
@scherrey
@uak_gitlab everything good now? yeah we don't check your headers at all except that the request is conformant https.
Damascene
@uak_gitlab
ok in python but there seem to be an issue with mint.bitcoin.com it couldn't use your api
Ben Scherrey
@scherrey
Do you know what the calls are that it's making?
Damascene
@uak_gitlab
unfortunately I'm not experienced with it. It was just a way to test compatibility. not critical for my work. just wanted to report it to you.
Napat
@SuperCipher
@scherrey
Have you remove a python src on ActorForth repo.
2 replies
Soichi Sumi
@soichisumi
Hi, when is BCHN May 2021 upgrade is completed?(in block height or other condition)
Soichi Sumi
@soichisumi
From BitcoinABC, the median time of the last 11 blocks is over timestamp 1621080000 (12:00:00 UTC), is the condition.
Ben Scherrey
@scherrey
@soichisumi you know I'm not 100% certain. I suspect it should be the same point as BCHN but BCHN may actually have already deployed the changes live since it won't break backwards compatibility, it will only allow things that previously would not be allowed.
Ben Scherrey
@scherrey
Sorry I meant to say "same point at BitcoinABC"...
anirudhab
@anirudhab
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.
Soichi Sumi
@soichisumi
@scherrey Sorry for the late reply. Your advice helped me to face the upgrade with peace of mind. thank you!
Ben Scherrey
@scherrey
@soichisumi glad to hear it! Anticipating our future upgrades go so well! :-)
@anirudhab we think we may have found your issue. Will have more information shortly.
Ben Scherrey
@scherrey
@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
Damascene
@uak_gitlab
1 reply
effgee
@effgee:matrix.org
[m]
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.
effgee
@effgee:matrix.org
[m]
That would be this: simpleledger/Electron-Cash-SLP#209 which is related to this feature: simpleledger/Electron-Cash-SLP#93
Nicolai Skye
@nicolaiskye
Hello @effgee:matrix.org , thank you for bringing these issues to our attention. We'll look into it further and let you know once we've resolved any of these bugs.
effgee
@effgee:matrix.org
[m]
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
Nicolai Skye
@nicolaiskye

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.

ActorForth/ECash-SLPDB#5

1 reply
effgee
@effgee:matrix.org
[m]
Should I just start making Github issues with full details?
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
effgee
@effgee:matrix.org
[m]
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.
effgee
@effgee:matrix.org
[m]
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
Ben Scherrey
@scherrey
@effgee:matrix.org unfortunately it appears that these issues are in existing SLP code that we've never touched so aren't terribly familiar with it. Someone who's more familiar with that code base from the Electron Cash SLP project is gonna have to look at it.
effgee
@effgee:matrix.org
[m]
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.
Ben Scherrey
@scherrey
Seems you've been busy digging. :-) One of the issues with SLP is certainly the lack of stability of the infrastructure. We're working on that as well.
effgee
@effgee:matrix.org
[m]
That is great to hear.
ahem read
Prashant Singh Pawar
@prashantpawar
Hey guys, I was directed here by @scherrey from SmartBCH telegram. I was wondering how is ActorForth (not he language but the REST services) different from FullStack.cash?
Ben Scherrey
@scherrey
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