Mark Logan

620 posts

Mark Logan

Mark Logan

@technicaldebtor

The dark side of the force is a pathway to many abilities that some consider to be unnatural

เข้าร่วม Şubat 2013
165 กำลังติดตาม681 ผู้ติดตาม
Mark Logan รีทวีตแล้ว
theficouple
theficouple@theficouple·
Reminder for all young parents: You only get: - 1 Summer with your baby - 3 with your toddler - 9 with your child - 5 with your teenager This time is precious. Don’t rush it.
English
158
2.5K
28.7K
926.6K
eye zen hour 🥶
eye zen hour 🥶@eyezenhour·
@b1ackd0g @technicaldebtor just curious, when you guys were researching the errors and thinking of solutions to fix it, was there any utilization of AI or an agent to provide feedback or conduct some of the troubleshooting research? or draft initial code? genuinely just curious as an AI user
English
3
0
11
1.8K
Sui
Sui@SuiNetwork·
We're live. Following last week's outages related to the 1.72 release, join @EmanAbio and @b1ackd0g as they walk through what happened and the steps taken to restore the network. @technicaldebtor from the Sui Core Team is also joining to add technical context. x.com/i/broadcasts/1…
English
65
84
559
121.8K
Mark Logan
Mark Logan@technicaldebtor·
I'm one of the people most directly responsible for this outage. I take Sui outages extremely personally and am incredibly disappointed that this happened. I'll echo what @EvanWeb3 said: Moving fast is no excuse for outages. This outage was caused primarily by an edge case in gas smashing introduced by address balances. However, we did not ship this feature carelessly. We spent over 6 months testing address balances and tried as hard as we could to exercise every edge case and combination of features we could think of. Unfortunately, we were bitten by an edge case that we did not discover during testing. Again, this is not an excuse - it shows that our testing strategy was inadequate, despite how much effort we put into it. We did not have a systematic way to enumerate or discover all possible edge cases. We will be re-examining our approach in light of this. But I do want to emphasize that we did not ship this feature carelessly or in a rush. We made mistakes, but we were absolutely not operating in "move fast and break things" mode. One more thing: Address Balances is by far the biggest change to Sui's execution model that we have shipped, and we don't have any plans to ship anything this large and disruptive again. It was a necessary change to make Sui into what it should be, but we don't seek out huge disruptive changes like this for the sake of it. Now that the feature is out we will be redoubling our efforts to make Sui the most reliable L1. We have a lot of work to do, I'm excited to start on it!
evan.sui@EvanWeb3

Moving fast is not a valid excuse for the outages. They are unacceptable, period. You have my sincerest apologies for the outages. We are focused on restoring the level of reliability and security to the absolute maximum.

English
111
101
595
112.9K
Mark Logan
Mark Logan@technicaldebtor·
@Lidlmedewerker1 @EvanWeb3 Confidential transactions are implemented entirely in Move and don't require any core level changes, so it's highly unlikely they will introduce any instability.
English
3
1
26
1.6K
Lidl
Lidl@Lidlmedewerker1·
@technicaldebtor @EvanWeb3 How big of an update would you consider the private transactions update that is coming soon?
English
1
0
8
1.7K
Mark Logan
Mark Logan@technicaldebtor·
@MrBreadSmith @kucoincom @BC_KuCoin @0xd34th Hey there - the funds are not lost. If you look at the transaction in an explorer (suivision.xyz) you will see the transfer, and if you look at the destination account you will see the funds. Once KuCoin fixes their issue you will be able to see the funds
English
0
0
1
259
MrBreadSmith
MrBreadSmith@MrBreadSmith·
Transfered USDC to Kucoin via Sui Network & completely lost it coz apparently they dont support “New Gasless Transfer” feature Please fix this issue! @kucoincom @BC_Kucoin @0xd34th
English
21
7
75
11.9K
Mark Logan
Mark Logan@technicaldebtor·
Even ignoring the formal verification angle, "AI is good at finding bugs so software will always be insecure" is fundamentally a very weird idea that stops making sense if you think about it for 2 minutes
vitalik.eth@VitalikButerin

Many people have claimed that with AI-assisted bug finding, secure code (and hence trustless anything) will be impossible. I have a much more optimistic take, and AI-assisted formal verification is a major part of the reason why: vitalik.eth.limo/general/2026/0…

English
0
0
4
2K
Mark Logan
Mark Logan@technicaldebtor·
Postel's Law (Be conservative in what you emit, liberal in what you accept) is bad advice. It's infinitely harder to make your software stricter in the future than to make it looser, so start out as strict as you possible can be.
English
0
0
3
845
Mark Logan
Mark Logan@technicaldebtor·
Something people don't understand about LLMs and security: It's not an arms race. Once you fix all the bugs, you win. Defender has the advantage! There is no AI model powerful enough to find bugs that don't exist.
English
0
0
0
627
Mark Logan รีทวีตแล้ว
Unconfirmed Labs
Unconfirmed Labs@unconfirmedlabs·
We've been working on a more scalable read and write layer for @SuiNetwork. Our solution, codenamed Hikari, is a near-parity drop-in replacement for Sui gRPC nodes, and unsupported requests automatically fall back to a full node. On the read side, we designed a custom storage backend that's fronted by multiple layers of caching, each serving a unique purpose. In our benchmarks for GetCheckpoint and GetTransaction requests conducted in 5 regions around the world, we're seeing the following p90 results: - Baseline Full Node: 400ms - Hikari (Origin): 54ms - Hikari (L3 Cache): 42ms - Hikari (L2 cache): 37ms - Hikari (L1 cache): 28ms - Hikari (L0 cache): 20ms That's a 22x improvement in latency. For writes (transaction submission), we implemented a lightweight service that's edge-deployable. Furthermore, unlike full nodes, Hikari can be horizontally scaled up in seconds. We benchmarked Hikari against fullnode.mainnet.sui.io across 5 regions, and achieved a 15-25% faster p90. We are working closely with the @CodaNetwork team to pilot Hikari. After a successful testing period, we will make Hikari available for the broader ecosystem.
English
2
4
36
2.5K
Mark Logan รีทวีตแล้ว
Terrible Maps
Terrible Maps@TerribleMaps·
The Pacific Ocean is so vast it could hold 16 Polands
Terrible Maps tweet media
English
344
2.3K
55.9K
7M
Mark Logan
Mark Logan@technicaldebtor·
@FFmpeg The real problem with GC is that it is non-local. If you have code that is slow because of calling malloc(), you can remove the malloc(). If you have GC pauses, the cause of that is the _entire rest of the program_
English
0
0
23
9.6K
FFmpeg
FFmpeg@FFmpeg·
This is the reason FFmpeg is not written in a Garbage Collected language. We can't just stall for a few milliseconds. Also unlike gaming which can just lag and reduce FPS, video (de)compression must maintain real-time to have smooth video. 1ms is a lot but it isn't at the same time.
Sebastian Aaltonen@SebAaltonen

Same is true for time. 1ms is a lot in real-time software. 120Hz displays (new phones) = 8.33ms budget. 1ms = 12% of your whole budget. I remember an old article saying that garbage collection is a solved problem, because it just takes couple of milliseconds...

English
73
290
5.5K
731.2K