You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integrate the Send to Lightning Address API as a Trigger.dev integration package. To read more about Trigger.dev Integrations read this: https://trigger.dev/docs/integrations/create. The idea is to be able to run ZBD payments from inside a Trigger.dev job by calling const response = await io.zbd.sendLightningAddressPayment() (or something of the sort).
Part of the integration code has been added on PR #1 but it has not been finalized nor tested.
Note: The user @rishi-raj-jain is already attempting to complete issue #2 and claim the bounty. If you attempt to complete the same issue, there is a chance that @rishi-raj-jain will complete the issue first, and be awarded the bounty. We recommend discussing with @rishi-raj-jain and potentially collaborating on the same solution versus creating an alternate solution.
@andrerfneves im confident i can tackle this, i've a lot of experience in blockchain development. I currently half time work at an l2 ethereum based company, and a couple years ago i was working in ethereum infrastructure development. I'm confident i can tackle this, but it looks like there was a solution before that was entirely ignored, and i've had many experiences like that with algora bounties before - where not even feedback is provided.
The bounty is too low to take such a risk so i would just like some confirmation you would actually be looking at the solutions before i attempt one
HELLO, sorry about the missed attempts. I thought this was for something else. I'm not sure if you know me from ZBD, been a member for years now. I am in college, and I have taught myself javaScript, Python, and Json. And a select few others. I am a Cyber Security Specialist in training, and a pen tester. But hard times, especially with technology and being open-source, I have to make money. And being a supporter of ZBD, what better place then to build with you first of all. My business is slowly growing I guess. I'm with MooMoo and Simply Wall St now with a server, chats, etc, and a narrative for Simply. Now I wish to build with you.
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: oliver ***@***.***>
Sent: Saturday, February 22, 2025 4:22:36 PM
To: zebedeeio/trigger.dev ***@***.***>
Cc: Penguin ***@***.***>; Manual ***@***.***>
Subject: Re: [zebedeeio/trigger.dev] ZBD API Integration with Trigger.dev (Issue #2)
@andrerfneves<https://github.com/andrerfneves> im confident i can tackle this, i've a lot of experience in blockchain development. I currently half time work at an l2 ethereum based company, and a couple years ago i was working in ethereum infrastructure development. I'm confident i can tackle this, but it looks like there was a solution before that was entirely ignored, and i've had many experiences like that with algora bounties before - where not even feedback is provided.
The bounty is too low to take such a risk so i would just like some confirmation you would actually be looking at the solutions before i attempt a solution
—
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLGS2COFAVHTDKXO7A7VRNT2RDTBZAVCNFSM6AAAAABXUUGGGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGQYDOOBZGU>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
[oliverqx]oliverqx left a comment (zbdpay/trigger.dev#2)<#2 (comment)>
@andrerfneves<https://github.com/andrerfneves> im confident i can tackle this, i've a lot of experience in blockchain development. I currently half time work at an l2 ethereum based company, and a couple years ago i was working in ethereum infrastructure development. I'm confident i can tackle this, but it looks like there was a solution before that was entirely ignored, and i've had many experiences like that with algora bounties before - where not even feedback is provided.
The bounty is too low to take such a risk so i would just like some confirmation you would actually be looking at the solutions before i attempt a solution
—
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLGS2COFAVHTDKXO7A7VRNT2RDTBZAVCNFSM6AAAAABXUUGGGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGQYDOOBZGU>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
I have a local patch that updates the existing ZBD integration to the current Trigger.dev integration API, wires sendLightningAddressPayment through io.runTask, uses the exported zbd client from @zbd/node, and validates with pnpm --filter @trigger.dev/zbd build on Node 18.
Hi, is this bounty still active and being reviewed? Before spending implementation time, I want to confirm the expected target: should a solution update this fork and be ready for upstream triggerdotdev/trigger.dev, or should the PR target upstream directly? I can include build/test evidence, but I do not want to duplicate a recent attempt if review is paused.
Activity
andrerfneves commentedon Oct 14, 2023
/bounty 30
algora-pbc commentedon Oct 14, 2023
💎 $30 bounty • ZBD
💎 $10 bounty • valerka11132
💎 $30 bounty • wercjk
Steps to solve:
/attempt #2with your implementation plan/claim #2in the PR body to claim the bountyThank you for contributing to zebedeeio/trigger.dev!
Add a bounty • Share on socials
andrerfneves commentedon Oct 14, 2023
Make sure to build upon the #1 PR: #1
rishi-raj-jain commentedon Oct 14, 2023
/attempt #2
Options
XooTB commentedon Oct 28, 2023
/attempt #2
Options
algora-pbc commentedon Oct 28, 2023
Note: The user @rishi-raj-jain is already attempting to complete issue #2 and claim the bounty. If you attempt to complete the same issue, there is a chance that @rishi-raj-jain will complete the issue first, and be awarded the bounty. We recommend discussing with @rishi-raj-jain and potentially collaborating on the same solution versus creating an alternate solution.
mrkirthi-24 commentedon Oct 31, 2023
Hey @rishi-raj-jain are you working on this??
rishi-raj-jain commentedon Oct 31, 2023
@mrkirthi-24
Feel free to take this...
ishqDehlvi commentedon Nov 13, 2023
Hey @rishi-raj-jain @mrkirthi-24 Are you working on this??
rajdip-b commentedon Nov 24, 2023
/attempt #2
Options
algora-pbc commentedon Dec 6, 2023
💡 @rajdip-b submitted a pull request that claims the bounty. You can visit your bounty board to reward.
rajdip-b commentedon Dec 8, 2023
@andrerfneves hey, can you review the PR?
shailedrathakur300 commentedon Feb 22, 2025
/attempt #2
Options
oliverqx commentedon Feb 22, 2025
@andrerfneves im confident i can tackle this, i've a lot of experience in blockchain development. I currently half time work at an l2 ethereum based company, and a couple years ago i was working in ethereum infrastructure development. I'm confident i can tackle this, but it looks like there was a solution before that was entirely ignored, and i've had many experiences like that with algora bounties before - where not even feedback is provided.
The bounty is too low to take such a risk so i would just like some confirmation you would actually be looking at the solutions before i attempt one
DailyInvestors commentedon Feb 24, 2025
AgentGoose32 commentedon Apr 28, 2026
/attempt #2
I have a local patch that updates the existing ZBD integration to the current Trigger.dev integration API, wires
sendLightningAddressPaymentthroughio.runTask, uses the exportedzbdclient from@zbd/node, and validates withpnpm --filter @trigger.dev/zbd buildon Node 18.hesong0222-dev commentedon May 13, 2026
Hi, is this bounty still active and being reviewed? Before spending implementation time, I want to confirm the expected target: should a solution update this fork and be ready for upstream triggerdotdev/trigger.dev, or should the PR target upstream directly? I can include build/test evidence, but I do not want to duplicate a recent attempt if review is paused.
andrerfneves commentedon May 13, 2026
Not live at this time sorry