John Cantrell

Any updated thoughts on this after talking with Nakamoto folk? I'm interested in working on this whether it's from scratch or implementing Nakamoto as a blockchain backend for bdk.

The bdk-ldk library https://github.com/johncantrell97/bdk-ldk has implemented: lightning::chain::chaininterface::BroadcasterInterface lightning::chain::chaininterface::FeeEstimator lightning::chain::Filter lightning::chain::Confirm I've looked at KeysInterface and I'm not entirely sure it's useful to implement with BDK. The only benefit that is...

It's definitely intended to be and currently usable as a library. The example bdk/ldk node I have and the more production ready node I'm working on are both using the...

Yeah that's a good question. Well it starts with needing to instantiate a bdk wallet which can definitely already be done in Kotlin. I haven't been closely following the language...

fwiw I'm seeing exactly the same thing and would love to know if there's a way to improve this.

The schema also has a unique constraint on organizationId, invitedEmail on the Membership table but then says it will clear invitedEmail once the User is set. Won't this cause a...

Also noticed the type for roles in session publicData is incorrect. Needs to be union of UserRole and GlobalRole instead of an intersection.

Had a question about this: ``` const project = await db.project.update({ where: { id, // Filter by organizationId organizationId: ctx.session.orgId, }, data, }) ``` To get this to work I...

In a multitenant setup would it make sense to create a combined authorize resolver instead of writing it all over the place? Something like: const authorize = resolver.pipe( resolver.authorize(), setDefaultOrganizationId,...

well, right now the nodes can open real channels to any node on the network (including the root node). I guess in theory we could add hosted channels as an...