• Built: @NotCentralised | @AusDeFi | @SIKE_AI | @ETFtrackerAU • Saying things: @ausbiztv • Advising: @dsaicommunity @the_buidersclub

Joined June 2011
1,522 Photos and videos
Pinned Tweet
10 Jul 2025
as part of @RBAInfo @DigiFinanceCRC Project Acacia, here's a primer on pubilc versus permissioned DLTs (distributed ledger technology), and on the back of the @RedbellyNetwork Insights podcast on right now (see x.com/RedbellyNetwork/status…), here's some explainers First up Public vs Private DLT Private Permissioned DLT: - Only selected, known participants (such as specific banks or financial institutions) are allowed to join and validate transactions. - Access is tightly controlled and not open to the general public; every participant is vetted and given explicit permission to participate. - Used when confidentiality and control are top priorities, often for sensitive financial transactions. Public Permissioned DLT (think more eligibility criteria which depends on market as @RedbellyAlan mentions in the show): - The underlying platform is open and potentially accessible to anyone for certain functions (like reading the blockchain or using apps), but only approved participants can validate transactions or issue assets. - A wider group can interact with the platform, but core functions (like settling tokenised assets or issuing CBDC) are restricted to those given explicit permission. - Balances transparency and openness with the need for regulatory control and permissioned access. In summary: So in summary - Private permissioned = access and participation are tightly restricted to a closed group. - Public permissioned = the network is broadly accessible, but only whitelisted participants can perform critical functions.

Redbelly Insights - Episode 11 x.com/i/broadcasts/1kvJpyoyR…
4
6
40
2,697
1/ something I shared on LI but HTML needs to be the way more things are shared as outputs from AI tools, apps, etc. Export to HTML as a default rather than .DOCX .MD .YAML etc - richer for agents to analyse and better for humans too
1
64
2/ sure it has it's drawbacks for editing etc but it's a pretty good uplift if understanding and quick analysis is your goal - here's an app we're testing in-house at @MadisonMarcusAU - has an export to HTML button
1
43
3/ you can see that with HTML you can bring over rich formatting and interactivity options to an offline format that you can read on any device (if you've designed it as such)
41
Mark Monfort retweeted
Community AMA w. Alan Burt x.com/i/broadcasts/1YGNrZyEz…
4
20
84
4,219
A reminder to read and understand the plans of your AI coding assistant before executing (which is easier if you have it ask permissions as it goes along)... lest you have it mistakenly try to overwrite things outside of what you asked for. If you don't read it, you can't understand if it's heading in the wrong direction and you can't do that if you don't at least have some understanding of the system you're building. This is where EXPERTS in the loop makes a difference vs just theprototypical HUMANS in the loop etc
1
54
The fact this sort of thing now makes it easier to generate deep fakes is pretty scary but hey, number go up
2
66
the fact that there are very few telltale AI artefacts in the image generation of the new @OpenAI image model is both exciting and scary... Anyway, well done ChatGPT but catch me tonight at the @AnthropicAI Claude Community Australia event at 8pm - link: luma.com/g3dhzsna
72
1/ Launched EITL.show (formerly @DigitalNexus) as it's own site this week with @digisincas
2
1
1
126
2/ check out the amazing guests covering key leaders and builders in the AI space in Australia
1
76
New Prompt: "Hey Claude, make me an app that will make a billion dollars... remember all of our previous billion dollar app conversations and DO BETTER" But seriously, very good things come from good context, memory and all... @AnthropicAI @claudeai @foundrylabsau @AusDeFi
1
1
83
What up buddy! Interesting new thing I noticed @claudeai has in code - what have you just hatched?
1
1
91
Yesterday, we officially launched @foundrylabsau Built for a world where AI is operational, data is messy, and trust actually matters. We focus on turning emerging tech into real systems, designed for production, with governance and auditability baked in, not added later. Less hype. More execution. More soon.
1
2
8
343
2026 is a time for change and my personal newsletter (running for a few years) is one of them... now it'll be monthly and jam-packed with a lot of what I'm thinking, building and more - check it out here: linkedin.com/pulse/founders-…
1
3
172
live right now with @RedbellyNetwork CEO @RedbellyAlan and #MattHale for Redbelly Insights - filmed in studio (thanks to @FEX_GLOBAL @foundrylabsau)
Redbelly Insights - Episode 23 x.com/i/broadcasts/1vOGwdjDQ…
1
2
12
515
1/ New blog with @VincentGramoli from @RedbellyNetwork - covers a talk we had and the theme of Why Predictability Beats Hype .. and why blockchain keeps repeating the same mistakes.
2
6
20
2,488
3/ The future of blockchain probably won’t look revolutionary. It will look… reliable. Quiet systems, stable costs, clear outcomes. That’s when people stop talking about the tech and just start using it. Why Predictability Beats Hype is now live.
1
1
7
146