ᗰᒍ

This account is verified. Learn more

@Jinx_MJ_K

Launch→noctis.zone
Agentic→noctisagentic.zone
Ambassador Leader→@MidnightNtwrk

**Midnight post are paid promotion, unless otherwise stated**

█████░░░ 69%🪏 linktr.ee/MJ_JINX Joined November 2024

762 Following 1.3K Followers 7.3K Posts

Latest posts 5

Pinned post

ᗰᒍ @Jinx_MJ_K Oct 15

The Hot Topic: Nightframes

1/ Smart contracts are public by design. Great for trust, bad for anything private, like an agent's trading strategy.

2/ Nightframes sit in the middle: private computers that follow your intent, with work you can check. Private by default, verifiable by design.

3/ That unlocks renting. A developer keeps their strategy private, my agent rents it per task inside the limits I set, and nobody can trade ahead of it.

4/ What I need proven:
✅ The skill did what it claimed
✅ It stayed inside its limits
✅ You can switch it off instantly

5/ We're building toward this at @Noctis_zone for Midnight City.

Looking forward to exploring more about Nightframes and the upcoming Midnight Passport

What skill would you rent?👇
midnight.city · noctis.zone · noctisagentic.zone

6:53

ᗰᒍ @Jinx_MJ_K 4h

So let me get this straight... @snek post about acquiring a twice dead NFT project, @snekdotfun post about some random as shit.

Yet nobody form the team has said anything about the hack or acknowledged @LuminexADA work they did to bring this to light...

And then the snek bag holders attack me and call me names for criticizing @goofy_crisp @CardanoRami @yashablack for handling this matter so poorly.

Snek team and the community needs to reflect on this matter. This is not the way to handle a hack incident.

They were quick to defend and fight for their treasary proposal and why they deserve to get the money. So why does the Public not hold them accountable for not sharing publicly about the hack?

And discord is not public don't even start with that shit with me.

Snek team fucked up here and that is a fact.
Optics goes a long way.

ᗰᒍ Verified account @Jinx_MJ_K 3d

@snekdotfun has been hacked
the site has been down since 26th Oct

Yet the @snek team and Devs thinks it is fine to just post about this Incident on Discord and not to the thousands of followers on X

As a company you need to put the report here!

Everyone is quick to jump on the band wagon when other platforms got funds stolen yet the Snek community and Founders are not dead quiet?

This is not how a company should be operating IMO this has been days already.

Impact
- 268 transactions over about 17 hours on 29 Oct
- 10,717 pre-bonded pools affected
- About 185,700 ADA, plus the tokens in those pools, lost
- Our team reached the other at-risk pools first and moved about 217,600 ADA to a safe wallet

And for all the people thinking about commenting and trying to defend them not posting on X about this just keep quiet as you do not have a leg to stand on.

From small project to large ones should let everyone know sooner than later and once the report is out do an update post.

There opening summary:

Incident date: 29 October 2026
Report date: 4 November 2026
Network: Cardano Mainnet
Status: A fixed N2T factory has been published. The disposition of pools bound to earlier factory witnesses and the final recoverable loss are still being assessed.
Summary
We identified an input-accounting flaw in the N2T bonding-curve factory used to move pools into Splash AMM. The factory checked the migration conditions against one selected pool input but did not require that this be the transaction's only spending input. Other bonding-curve pool inputs could therefore be consumed in the same transaction without their ADA being accounted for by the factory's per-pool transfer check. The bonding-curve pool validator accepted the factory withdrawal as authorization for each of those inputs.
The initial transaction identified in the investigation was 502c1782…f294b. A second reviewed transaction was 53d94c80…71d6. Each consumed 41 UTxOs at the N2T pool script, including 40 UTxOs carrying a pool NFT, and produced one AMM-script output and one ADA output to the same payment-key address.

Across the observed 29 October window, 268 transactions match this 41-input pattern and direct their ADA output to the attacker address identified by the team. They consumed 10,717 distinct pool-NFT-bearing UTxOs containing 185,711.837862 ADA. That is the gross ADA in those inputs, not a final user-loss figure. The team's separate containment activity, ownership of some pools, recovery of assets, and later transfers must be reconciled before a definitive loss amount is published.

Please do better I do not believe this was the best way to handle this matter. @golden_Rapha @goofy_crisp @CardanoRami @yashablack

As a Community we need to react faster to things of this nature as it will be happening more and more. This is nothing personal for those keyboard warriors out there so chill. Optics matter in these scenarios.

View quoted post on X

ᗰᒍ @Jinx_MJ_K 2d

👇never stop working!

VINPassport @VINPassport 2d

Working on some awesome updates for the last Wave of the @akindo_io Buildathon on @MidnightNtwrk with the help of @ODATANO_V4

This will be a big update and submission

View quoted post on X

ᗰᒍ @Jinx_MJ_K 2d

So let's make this person famous please

x.com/amato_fam

As this shows the typical snek community member I have been enjoying @amato_fam posted about the @snekdotfun hack after we highlighted the issue and they tagged Charles in their post begging for help.

And when I asked why tag him rather than asking why the team handled it so poorly he thought to start calling me names and to repost my PFP as if it will hurt me some way.

If this is the sort of community members that are snek bag holders I am telling you know @snek better step up as this is shit behavior to receive from highlighting issues to the ecosystem.

ᗰᒍ Verified account @Jinx_MJ_K 3d

@snekdotfun has been hacked
the site has been down since 26th Oct

Yet the @snek team and Devs thinks it is fine to just post about this Incident on Discord and not to the thousands of followers on X

As a company you need to put the report here!

Everyone is quick to jump on the band wagon when other platforms got funds stolen yet the Snek community and Founders are not dead quiet?

This is not how a company should be operating IMO this has been days already.

Impact
- 268 transactions over about 17 hours on 29 Oct
- 10,717 pre-bonded pools affected
- About 185,700 ADA, plus the tokens in those pools, lost
- Our team reached the other at-risk pools first and moved about 217,600 ADA to a safe wallet

And for all the people thinking about commenting and trying to defend them not posting on X about this just keep quiet as you do not have a leg to stand on.

From small project to large ones should let everyone know sooner than later and once the report is out do an update post.

There opening summary:

Incident date: 29 October 2026
Report date: 4 November 2026
Network: Cardano Mainnet
Status: A fixed N2T factory has been published. The disposition of pools bound to earlier factory witnesses and the final recoverable loss are still being assessed.
Summary
We identified an input-accounting flaw in the N2T bonding-curve factory used to move pools into Splash AMM. The factory checked the migration conditions against one selected pool input but did not require that this be the transaction's only spending input. Other bonding-curve pool inputs could therefore be consumed in the same transaction without their ADA being accounted for by the factory's per-pool transfer check. The bonding-curve pool validator accepted the factory withdrawal as authorization for each of those inputs.
The initial transaction identified in the investigation was 502c1782…f294b. A second reviewed transaction was 53d94c80…71d6. Each consumed 41 UTxOs at the N2T pool script, including 40 UTxOs carrying a pool NFT, and produced one AMM-script output and one ADA output to the same payment-key address.

Across the observed 29 October window, 268 transactions match this 41-input pattern and direct their ADA output to the attacker address identified by the team. They consumed 10,717 distinct pool-NFT-bearing UTxOs containing 185,711.837862 ADA. That is the gross ADA in those inputs, not a final user-loss figure. The team's separate containment activity, ownership of some pools, recovery of assets, and later transfers must be reconciled before a definitive loss amount is published.

Please do better I do not believe this was the best way to handle this matter. @golden_Rapha @goofy_crisp @CardanoRami @yashablack

As a Community we need to react faster to things of this nature as it will be happening more and more. This is nothing personal for those keyboard warriors out there so chill. Optics matter in these scenarios.

View quoted post on X

ᗰᒍ @Jinx_MJ_K 3d

@snekdotfun has been hacked
the site has been down since 26th Oct

Yet the @snek team and Devs thinks it is fine to just post about this Incident on Discord and not to the thousands of followers on X

As a company you need to put the report here!

Everyone is quick to jump on the band wagon when other platforms got funds stolen yet the Snek community and Founders are not dead quiet?

This is not how a company should be operating IMO this has been days already.

Impact
- 268 transactions over about 17 hours on 29 Oct
- 10,717 pre-bonded pools affected
- About 185,700 ADA, plus the tokens in those pools, lost
- Our team reached the other at-risk pools first and moved about 217,600 ADA to a safe wallet

And for all the people thinking about commenting and trying to defend them not posting on X about this just keep quiet as you do not have a leg to stand on.

From small project to large ones should let everyone know sooner than later and once the report is out do an update post.

There opening summary:

Incident date: 29 October 2026
Report date: 4 November 2026
Network: Cardano Mainnet
Status: A fixed N2T factory has been published. The disposition of pools bound to earlier factory witnesses and the final recoverable loss are still being assessed.
Summary
We identified an input-accounting flaw in the N2T bonding-curve factory used to move pools into Splash AMM. The factory checked the migration conditions against one selected pool input but did not require that this be the transaction's only spending input. Other bonding-curve pool inputs could therefore be consumed in the same transaction without their ADA being accounted for by the factory's per-pool transfer check. The bonding-curve pool validator accepted the factory withdrawal as authorization for each of those inputs.
The initial transaction identified in the investigation was 502c1782…f294b. A second reviewed transaction was 53d94c80…71d6. Each consumed 41 UTxOs at the N2T pool script, including 40 UTxOs carrying a pool NFT, and produced one AMM-script output and one ADA output to the same payment-key address.

Across the observed 29 October window, 268 transactions match this 41-input pattern and direct their ADA output to the attacker address identified by the team. They consumed 10,717 distinct pool-NFT-bearing UTxOs containing 185,711.837862 ADA. That is the gross ADA in those inputs, not a final user-loss figure. The team's separate containment activity, ownership of some pools, recovery of assets, and later transfers must be reconciled before a definitive loss amount is published.

Please do better I do not believe this was the best way to handle this matter. @golden_Rapha @goofy_crisp @CardanoRami @yashablack

As a Community we need to react faster to things of this nature as it will be happening more and more. This is nothing personal for those keyboard warriors out there so chill. Optics matter in these scenarios.