Аналитика Telegram-канала
Подписчики
4 183
Охват за 24 ч
108
ER за 24 ч
2,58%
Публикаций
496
Динамика подписчиков
7 дней
30 дней
6 месяцев
Больше
16 ноя19 ноя22 ноя
Показаны последние 7 дней
Больше истории →
Охваты публикаций
11.1113.1115.1117.1118.1120.11
35
Средний охват
40
Лучший результат
Показаны 6 публикаций — последние в канале
Больше статистики →
Упоминания
191
Упоминаний
144
Из них репостов
17
Каналов
2
Упоминаний за 90 дней
0
Из них репостов
2
Каналов за 90 дней
Последние посты
3 из 496 2 из 496
Copying a nested recursive struct over its parent can corrupt storage.
Solidity 0.8.39 fixes this code-generation bug: the destination is a recursive struct in storage, and the source is a struct nested inside it. The fix adds a runtime overlap check when copying recursive structs between storage locations and takes a memory snapshot of the source when the target contains it.
Before shipping, review storage-to-storage assignments involving recursive structs. Check whether the source can be nested inside the destination; that is the overlap condition identified in the release. If it can, rebuild with 0.8.39 before deployment. The release notes do not specify the affected version range.
Before You Ship
Solidity 0.8.39 release notes
@soliditypedia
ещё
31
2
20 ноя, 15:15
Under proposed split gas accounting, gasleft() deltas would miss part of a call’s cost.
EIP-8037 separates execution gas from state gas, with a reservoir that GAS does not report. That would make sub-call metering, including ERC-4337 EntryPoint accounting, undercount costs paid from the reservoir.
EIP-8455 proposes RESERVOIR to expose that missing budget. Metering must compare GAS + RESERVOIR before and after a call: cross-frame refills can move gas between the pools, so either counter alone can misreport consumption.
This is a draft, not an available opcode. It preserves GAS for call forwarding; validation-time restrictions remain a coordination requirement for ERC-4337.
This Changes the Design
EIP-8455 proposal and discussion
@soliditypedia
ещё
34
2
1 18 ноя, 18:15
Check ID density before packing replay flags.
A bitmap shares one storage word across 256 flags only when IDs land together. Hash-derived nullifiers do not provide that locality; sparse sequence numbers leave capacity unused.
An Ethereum Research example packs four sessions into one word, with a 64-bit lane per session and one bit per operator. It rejects operator indices of 64 or more: a session with 70 operators does not fit.
Before choosing this layout, check sequence gaps and the maximum operator count. Enforce the index bound and reject an already-set bit. Choose lane width for supported sessions, not just average occupancy; wider lanes leave fewer sessions per word.
Before You Ship
Replay-flag packing discussion
@soliditypedia
ещё
33
2
1 17 ноя, 16:15
Продолжить анализ этого канала
- История роста подписчиков
- Просмотры и охваты публикаций
- Кто упоминает канал и кого упоминает он
- Похожие каналы и подбор для рекламы
Открыть аналитику
Демо до 14 дней