Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author gesman

    (@gesman)

    Should work with Electrum 2.5.4 MPK’s now.

    Plugin Author gesman

    (@gesman)

    Apologies.
    Confirm issues with 2.x Electrum, although I am gathering resources to implement support for Electrum 2.x right now.

    We are getting close.

    If you’re interested to help – please donate:
    1H9uAP3x439YvQDoKNGgSYCg3FmrYRzpD2

    Gleb

    Hi gesman, im very interested to help.. I had given up hope on this plugin so happy to see u back on the forum..

    What exactly is the intent here?

    1. Is there a new version somewhere (u mentioned inpt can now support mpk from elec 2.5.4 but i dont see anything new in the plugin).

    2. Are you planning to update the code to release new plugin? If so, mighto suggest pre selling a few pemium plugin licenses to fund the work?

    3. Is there a $ goal in mind to reach the resources needed?

    4. Have u been in touch with other devs who either forked ur original plugin or made similar plugins? It would seem like a good idea to leverage some of the work theyve done where possible.
    For example, i know one guy who hacked their way around to get the api stuff working again. Another who made it accept mpk version 2. Another who went way deeper into functionality based on some of the pain points of ur original plugin.

    Please share some info and i for one am happy to donate and support this project.

    Plugin Author gesman

    (@gesman)

    I’m working right now, as time permits to support both – older MPK and 2.x MPK transparently.
    In addition I plan the math logic to get a bit faster as well.

    I’d be happy to get resources and or more funding to accelerate the development.
    The goal is 3 BTC – if I reach it – I will release major update with fixes within 3 days.

    I definitely working on it already as time permits and already engaged help from other resources (regarding implementing new math) for which I had to pay from my pocket.

    Donations are here:
    12fFTMkeu3mcunCtGHtWb7o5BcWA9eFx7R

    Gleb

    You serious? You left the project for almost two years and now you ask 3BTC (1200USD) for an update?

    Although yo had to pay to get it work, i’m nog using your plugin anymore. There are better ways to use it with Woocommerce and yours ain’t on the list anymore.

    Plugin Author gesman

    (@gesman)

    Plugin updated and added support for both Electrum 1.x and 2.x MPK’s. Plus faster math library.

    Hey gesman, u left out release notes regarding confirmation checking. I see you changed that around quite a bit. But, ur notes are incorrect in the code as per how the blockexplorer.com api works. It actually will only show a non-zero balance once there is 1 confirmation. Until then it will always show 0, at least in my testing of their api … which lead me to modify your previous release code.

    Also, I see theres nothing logged if the balance returned is 0, I guess thats ok but being someone who prefers more verbose output to the log… could you add a log output for such scenario for not enough confirmations?

    Also, I see that you added your own sites blockexplorer query as primary query if selected as an option.

    Any other changes we should be informed of that didnt make it into the release notes?

    Plugin Author gesman

    (@gesman)

    You’re correct, I was deadly tired yesterday spending whole weekend for this update.
    I want to gather working API’s under one umbrella (the ones that could do confirmations checks) and call it first. Then blockchain.info. Then others.
    This way I don’t need to update the plugin every time something changes in someone’s API, leaving people with broken code.

    Still unfinished but it does not prevent code from being operational as is.
    The biggest show stopper was support for MPK 2.x – and now code supports both transparently.
    It makes sense for more detailed log outputs.

    gesman,

    if u get the plugin to a point where there are API selection choices (which i truly believe caused all the growing problems. I will donate $250. I hope u consider this fair considering the defunct nature of this project for last 2 years.

    I’ve been rooting for crowdsourcing to get u re-motivated about a year ago but since found workable alternatives. But I like urs best due to simplicity.

    Plugin Author gesman

    (@gesman)

    Hi Jerry,

    Actually it’s operational already.

    I’ll be improving it as time goes on but as of now – major bugs are fixed and everything back on track.

    so a non-coder could swap out the API providers? Maybe im looking at wrong version but i don’t see where.. and i remember that was the one thing that killed me..i know its probably very simple dev stuff but the common guy would just want a few settings fields..

    More generally, id like something self-sustainable.. i have to read recent forum posts but do u have an outline of what caused the breakdown to occur on the old version? I always assumed it was 90% API problems..

    Plugin Author gesman

    (@gesman)

    Non-coder wants to make sure his store is operating smoothly and processes payments without glitches.

    Non-coder does not need to swap API providers or do any other under the hood trickery.

    Previous glitches were due to multitude of bugs, inefficiencies and lack of important support of Electrum 2.x MPK.
    It’s all fixed now – see readme.txt.

    There are ideas for improvement – but remember it’s a free project and i working when i have time (which in most cases i don’t).

    I can only speak for myself but for a long time the plugin referenced 1.9.8 mpk to generate unique pay address. Showed qr code. But i always had an issue with getting the api to return confirmation vales and have status fields updated, i got alot of cloudflare problems.

    And i can tell u that other plugins suffer from the api problem too.. The api call limits seem to only like to accept X number of api calls a day and then they try to cut u off. And they fluctuate. So a api that works well today, might not work in a month.

    What api is used now? U dont think thats the cause of any problems with the old plugin using the blockchaininfo api ?

    Why was the electrum 2+ version mpk so important to get working? Its cool and all but i never really cared much that i had to use 198 v mpk.

    Lemme checkout readme,txt,

    Plugin Author gesman

    (@gesman)

    No it has nothing to do with blockchain API.
    Problem with blockchain API can only cause a slightly delayed confirmation of payment.
    The way I set API is that if one API service failed – it tries next service, and so on.

    Gonna give it a whirl and will report back and give u sccess to site if i still have issues.

    If it works, will be happily donating towards ur project.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Support for electrum 2.5.1 MPK’ is closed to new replies.