Magicians at 35c3


will other magicians attending 35c3? Perhaps we can have some spontaneous sessions there. We might perhaps be able to do this in theCritical Decentralisation Cluster or allocate some workshop room for some sessions. I will also bring some magician stickers to 35c3 - I can also bring some more so they can be relayed to local groups.


I’m down, Ligi :wink:



Should nothing go horribly wrong, I’ll be at the congress.


Great idea! We can either submit that as part of the CDC program or we can do it ad hoc in the chill-out setup.


I think we should do one session as part of the CDC program - ad-hoc sessions will happen anyway :wink:
Really want to make some people at #35c3 aware that they are Magicians as I think people from there could contribute and fit nicely in our ecosystem. Will also put a lot of these stickers on the sticker-tables - in the hope people check out what the Magicians are.


I’ll be there too and could help spread the stickers.


@cleanunicorn great!

and a small teaser:


the wiki for self organized sessions is now open:

Thinking about adding a session there - just not yet sure which room - I am undecided between these 2 options:

  • Seminar room 14-15, FCFS – with 66 square meters and 20 seats (banquette seating) - projector, tables
  • Lecture room M1, FCFS – with 118 square meters and 48 seats (classroom seating) – projector, tables

would prefer banquette seating - but this is for a max of 20 humans. Would keep the topic quite open like “Ethereum Magicians gathering at 35c3”

Also what length should we allocate? I would tend to 60min.

Also thinking about a session on the topic of ethereum key management (talking about hardware wallets, java-cards, …)

Other ideas or suggestions?


I’ll be there! and ready to help.
60 minutes is good. Key management as well. I think that some general education would be ace too, and what we have been doing at magi about it.
The 48 people room sounds good. I think if we talk key management we will have enough interested people.
I’d like us to cover burner wallets as well, this is an interesting topic for CCC, happy to present it.


Hey @ligi any updates on this? I have to opt-out Friday due to work, so im trying to work my fahrplan :slight_smile:


dam - I already registered for Friday a while ago - but just realized that I just posed it there:


Cool, ill be there! anything I can do to help?


great! Not that I am aware of - just wanted to have a loose gathering of magicians - don’t think there is a need for much preparation - but if you have ideas please shoot! Are you at location already.


Ah crap I just realized friday is 28th. Shit, I’ll try to come!



(This is just a personal recollection, for the sake of posterity; you’ll see shortly that it’s of parts where I participated myself (what a surprise!..). Phrases in quotes are not actual quotes, but me paraphrasing.)

The meeting lasted ~1 hour. There were ~30 (~50?..) people in the room, of various backgrounds - researchers, protocol developers, [d]application developers, auditors (security specialists?..), “generally interested”.

Of those present, ~10 (15?..) voiced one opinion or the other, or asked questions. Others participated in the “introduce yourself” part only.

The room was “almost big enough”, but there were not chairs for everybody. So, during several show-of-hands, we could’ve missed someone in the corner.

One person had a laptop open, but I’m not sure if they were taking notes, or just keeping an eye on the clock.

Two topics were discussed broadly: “state storage rent” and “governance”.

State storage rent

  • A mention of why state bloat is increasingly an issue was made.
  • A general description of “rent” was given.
  • Of everyone present, no one was against the idea “over my dead body” (via show-of-hands).
    • One person was willing to argue against rent if need be, for the sake of those not present. This was not explored.
  • “Stateless” contracts (of the “merkle proof” variety) were discussed, but not delved deep into (as they do not provide a mechanism to remove state entries “no longer wanted by anybody”?..).
  • It was noted that, indeed, all contracts would have to be rewritten under the new “rent paradigm”, as they’ve so far been written without the consideration.
  • Recent proposals by @AlexeyAkhunov were mentioned.
    • Of those present, only one person seemed to have at least some familiarity with those (via show-of-hands) - me, with the first one.
    • I tried to describe a non-essential facet of the proposal, as it related to the discussion at hand: namely, that a “rent balance” is introduced, how it is drawn from, and by whom. Think I butchered it.
    • The core of the proposal - namely, modification of the “storage layout” to allow for direct attribution of “who wrote what to the state”, using new opcodes, - was not discussed.
    • Alexey’s second proposal, revolving around CREATE2, was not discussed.
  • The issue with rent remaining for infrastructure/“commons” on-chain contracts, such as the ENS Registry (hash map) was mentioned.


  • Of those present, at least two were “satisfied with current governance in general” (via show-of-hands).
  • The need for a systemic/actionable approach to this broad topic was raised - namely, either:
    • identify undesirable aspects of the current system/process, and describe approaches to get rid of them; or
    • describe a desirable system/process, and then approaches to transition from one to the other.

(I was one of the two “already satisfied” people, so zoned out during most of the discussion. Someone else could provide a summary…)


There was a brief shuffle on the balcony, after which the participants dispersed throughout the congress. Assume undocumented “work in workgroups”.

A session (unrelated to the above) was organised by @chriseth, to present JuliaLang; was not there, can’t describe.

I’m aware of no other Ethereum-related sessions. Ping if you do.


Thank you so much for this write-up!

I have not got myself together to write the second version (needed to make some time for other things), but it will be done very soon.