<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="fr">
	<id>https://wiki.campuscyber.fr/index.php?action=history&amp;feed=atom&amp;title=Translations%3ACI_Crypto-actifs%2F20%2Fen</id>
	<title>Translations:CI Crypto-actifs/20/en - Historique des versions</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.campuscyber.fr/index.php?action=history&amp;feed=atom&amp;title=Translations%3ACI_Crypto-actifs%2F20%2Fen"/>
	<link rel="alternate" type="text/html" href="https://wiki.campuscyber.fr/index.php?title=Translations:CI_Crypto-actifs/20/en&amp;action=history"/>
	<updated>2026-06-14T04:25:22Z</updated>
	<subtitle>Historique des versions pour cette page sur le wiki</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://wiki.campuscyber.fr/index.php?title=Translations:CI_Crypto-actifs/20/en&amp;diff=7480&amp;oldid=prev</id>
		<title>FabienG : Page créée avec « &#039;&#039;&#039;On 13/04/23, the WG Crypto-assets worked on&#039;&#039;&#039;&#039;  * The Challenge Innovation use case. It emerged from the discussions that it would be interesting to develop a toolbox, a Web3 dashboard capable of managing and analysing incidents. A sort of Web3 SOC. * The ToE diagram for the Nodes target. It needs to be clarified and the fact that the consensus algo needs to be controlled needs to be made explicit. »</title>
		<link rel="alternate" type="text/html" href="https://wiki.campuscyber.fr/index.php?title=Translations:CI_Crypto-actifs/20/en&amp;diff=7480&amp;oldid=prev"/>
		<updated>2023-12-05T15:10:25Z</updated>

		<summary type="html">&lt;p&gt;Page créée avec « &amp;#039;&amp;#039;&amp;#039;On 13/04/23, the WG Crypto-assets worked on&amp;#039;&amp;#039;&amp;#039;&amp;#039;  * The Challenge Innovation use case. It emerged from the discussions that it would be interesting to develop a toolbox, a Web3 dashboard capable of managing and analysing incidents. A sort of Web3 SOC. * The ToE diagram for the Nodes target. It needs to be clarified and the fact that the consensus algo needs to be controlled needs to be made explicit. »&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Nouvelle page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;On 13/04/23, the WG Crypto-assets worked on&amp;#039;&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
* The Challenge Innovation use case. It emerged from the discussions that it would be interesting to develop a toolbox, a Web3 dashboard capable of managing and analysing incidents. A sort of Web3 SOC.&lt;br /&gt;
* The ToE diagram for the Nodes target. It needs to be clarified and the fact that the consensus algo needs to be controlled needs to be made explicit.&lt;/div&gt;</summary>
		<author><name>FabienG</name></author>
	</entry>
</feed>