Jeeya_Awan

Asumsi Kesulitan Diffie-Hellman:

Dalam setiap grup, logaritma diskret loдb a adalah bilangan x ∈ Z sedemikian sehingga bx = a.

Sebagian besar blok bangunan kriptografi yang terkait dengan pekerjaan ini dikaitkan dengan asumsi Diffie-Hellman yang menggunakan kesulitan logaritma diskret dalam grup siklik.

Mempertimbangkan grup siklik perkalian G dengan orde p dan generator д, kita
dapat merumuskan asumsi berikut: diberikan дa dan дb untuk a,b ∈ Zp yang dipilih secara seragam dan independen, maka дab berperilaku seperti elemen acak dalam G dengan orde p.

Jaringan @Dusk network menggunakan mata uang digital terdesentralisasi dan berfokus pada privasi yang berkembang dari protokol CryptoNote melalui penemuan menakjubkan di bidang konsensus Byzantine dan fungsi acak semu oleh para kriptografer terkemuka dunia seperti Silvio Micali, Michael Rabin, Alexander Yampolskiy, dan Evgeniy Dodis.

Dusk secara radikal berbeda dari blockchain lainnya dengan menerapkan mekanisme konsensus adaptif, yang disebut Segregated Byzantine Agreement (SBA), yang tidak memerlukan intensitas komputasi tinggi seperti proof-of-work dan merupakan alternatif yang lebih adil dibandingkan proof-of-stake.

By now you’ve probably noticed that @Dusk has rebranded! They're thrilled to have a new look that is sleeker, simpler, and more direct than before. The rebranding process is very detailed and in-depth, and throughout the process and subsequent rewriting of copy, three phrases are constantly present: Real-World Assets (RWAs), Compliance, and Privacy.
In many ways, these three sum up Dusk. They want to bring RWAs on-chain and to do that they must be compliant and private. Dusk is often called a privacy coin or at least put into the ZK rollup category. While dusk do care about privacy and do use zero-knowledge proof cryptography (they're not a rollup or Layer 2 though), it isn’t our end goal, and instead, they do this so that they can bring RWAs on-chain.
So, today let’s have a look at these three pillars, and how they benefit both businesses and users.

1) Compliance:
Compliance is hugely important for us and guides our decisions and infrastructure, as in order to interact with regulated assets we must meet their regulatory requirements. Financial institutions have to follow a huge amount of rules and regulations, and how they do this has thus far been built around centralized systems.
This has led to us developing tools like Citadel, a decentralized licensing protocol that can be used for everything from KYC/AML procedures to subscription plans. The twist is that it’s private, and operates using ZKPs, meaning users do not have to give away their personal data, while still being able to prove what is necessary to comply with the rules.
#Dusk has also make it easy for institutions and businesses to program and automate their compliance and follow policy. While this is a requirement for institutional adoption, it also is a strong business case in and of itself and can save companies huge amounts of money by automating and streamlining their processes.
While Dusk is business-friendly, their approach also benefits average users by returning custody, of their assets, data, and identity, to them while allowing them to engage with both classical assets and new ones.
Without compliance, we can have all the technology in the world but will never be able to use it in a meaningful way. A lot of blockchains are not capable of complying with GDPR, for example, and this will hinder business adoption.
Their founders were thinking about regulation and compliance long before it was cool, seeing that business adoption would require blockchain technology that’s capable of being compliant and legislation that is reasonable and allows blockchain to grow. At least in the EU, they have that.
2) Privacy:
Privacy is what they're best known for. Dusk use zero-knowledge proof cryptography, specifically PLONK, to ensure that transactions are verifiable and correct while being private.
Privacy is another necessity, both in general for all people and to facilitate mass adoption. Institutions will never tokenize their assets if every move they make is public, and regular people would also be hesitant to use blockchain in a meaningful way if it meant every transaction they’ve ever made was public.
This is what they're best known for, and while we care deeply about privacy as a right, we also recognize that it’s a necessity for blockchain to be used at scale and for things that matter.
Their approach ensures privacy while providing the auditability that institutions require, and in many cases provides higher standards of privacy than institutions and users are used to (by removing the need for third parties we provide higher levels of privacy).
Their novel approach to privacy and focus on the real world means that users are not constantly leaking data and can practice selective disclosure. Their goal with privacy is to match and then improve upon what is currently available.
3) Real-world assets:
These two points bring dusk to real-world assets. The ultimate goal of Dusk is to bring institutional-level assets to anyone’s wallet. This means users can move seamlessly between crypto and traditional assets and engage with traditional assets in the same way as they interact with crypto; trustlessless, permissionless, and with self-custody.
Bringing RWAs on-chain is good for businesses too, giving them faster settlement times, access to consolidated liquidity, and allowing them to use smart contracts for a lot of time (and money!) consuming processes.
Their goal is to deliver financial freedom and inclusion to all by improving the current systems and eliminating the inefficiencies they're all used to.

These three pillars make the digital world secure.
$DUSK

@Walrus 🦭/acc is a decentralized storage protocol based on erasure-coding. Anyone can interact with Walrus to store arbitrary data and prove that the data is stored. Like IPFS, Walrus itself is not a blockchain. However, Walrus leverages the Sui network for help with storage node lifecycle management, blob lifecycle management, and the introduction of incentive systems. Sui has achieved exceptionally high scalability compared to other blockchains with its own consensus and smart contracts. However, if Sui were to handle blobs in addition to transaction data, it would be inefficient as all nodes would replicate large volumes of blobs, greatly increasing the replication factor. Therefore, Walrus uses erasure-coding to divide blobs into smaller units called slivers and allocate them to nodes, allowing large volumes of data to be stored in a decentralized protocol with a replication factor of just 4-5. In particular, unlike existing decentralized storage protocols, #Walrus has the advantage of significantly reducing data recovery costs by using an encoding method called Red Stuff. So, what is Red Stuff
1) Encoding:

Red Stuff encodes the blob in two dimensions. This is for efficient sliver recovery. In the primary dimension, encoding is similar to RS-encoding, dividing B into f+1 primary slivers. Red Stuff goes a step further, dividing each of the f+1 primary slivers into 2f+1 secondary slivers in the secondary dimension. As a result, B becomes a matrix of (f+1) * (2f+1). Note that the example in the above figure assumes f=1. Based on this two-dimensional matrix, additional repair symbols are generated for both dimensions. Note that a symbol is a smaller unit of data than a sliver. First, the symbols of 2f+1 columns are expanded from f+1 to 3f+1, and then the symbols of f+1 rows are expanded from 2f+1 to 3f+1. The commitment to B can be easily calculated. W calculates commitments for each rows and columns including the additional repair symbols, then combines all these sliver commitments to create the blob commitment.
2) Write:
The process of storing data in the Walrus protocol is similar to protocols using existing RS encoding. W encodes the original data with Red Stuff to generate sliver pairs to send to each node. A sliver pair here refers to a pair of primary and secondary slivers, with a total of 3f+1 sliver pairs generated.
W then propagates 3f+1 sliver pairs and sliver commitments to 3f+1 nodes each. Upon receiving these, nodes verify the slivers through the commitments and send signatures back to W. When W receives 2f+1 signatures, it generates an availability certificate and publishes it on-chain (Sui network). This is because even if f Byzantine nodes sign, there are signatures from f+1 honest nodes, making it possible to recover the original data.
3) Read:
The process of reading data from Walrus is also identical to protocols using existing RS encoding, and only primary slivers need to be used. When R receives f+1 or more valid primary slivers from storage nodes, it can recover B and read the data.
4) Recovery;
The biggest advantage of Red Stuff compared to RS encoding is evident in the data recovery process. Assuming the network is in an asynchronous environment and nodes can freely enter and leave, there may be nodes that don't receive slivers from W. Therefore, these nodes need to communicate with other nodes to recover slivers.
Let's examine how a node that didn't receive slivers recovers data through the above figure (f=1).
a: Assume a situation where Node 1 fully possesses the first sliver pair, Node 3 has the third sliver pair, and Node 4 needs to recover the fourth sliver pair.
b: Nodes 1 and 3 send symbols that overlap with the fourth sliver pair (S14, S34, S41, S43) to Node 4.
c: Since Node 4 now has f+1 or more symbols for the fourth secondary sliver, it can recover the fourth secondary sliver. Extending this logic means that all 2f+1 honest nodes can recover their secondary slivers.
d: The fact that 2f+1 nodes all have secondary slivers means there are 2f+1 symbols in each row, which allows for the recovery of all primary slivers using these 2f+1 symbols. In conclusion, if f+1 or more nodes in the network have slivers, the remaining nodes can communicate with them to recover all slivers.
The size of a symbol is O(B/n^2), and each node needs to download O(n) symbols, so the recovery cost per node is O(B/n). Extending this to the entire network, the cost for all nodes to recover slivers corresponds to O(B). Considering that the cost of recovering data is O(n^2B) in the full replication method and O(nB) in the encode and share method, the Red Stuff method can process this very efficiently at a cost of O(B). In other words, the data recovery cost is constant regardless of the number of nodes (n) participating in the network.
• Walrus Storage Flow:
Red Stuff is one method of encoding data. Now, let's look at the big picture of how data storage occurs in Walrus, including interactions with Red Stuff and the Sui network.

A user wanting to store data in Walrus acquires storage resources. Storage resources can be purchased directly from the Walrus system object smart contract on the Sui network or from a secondary market. Storage resources can be understood as permissions to store data in Walrus, specifying the start epoch, end epoch, and how much capacity can be stored. The user applies Red Stuff encoding to the blob they want to store and computes the blob ID. Subsequent steps can be performed directly or by publishers existing in the network. To register the blob ID with the storage resource, the user updates the storage resource on the Sui network to trigger an event. The user propagates the blob metadata to all storage nodes and distributes each sliver to the respective nodes. Storage nodes receive the slivers and verify whether the metadata matches the blob ID and the slivers match the metadata, and if the user transmitting the sliver has appropriate storage resources. If deemed valid, storage nodes send signatures for the respective slivers to the user. When the user receives 2f+1 or more signatures, they generate an availability certificate and transmit it to the Sui network. From this point, the PoA (point of availability) status is updated on the Sui network, indicating that the blob is available to everyone. If there are storage nodes that haven't received slivers for that blob even after confirming the PoA, they can sync with other storage nodes to recover the slivers. Note that the Walrus protocol has an epoch concept for a certain period, and the set of participating storage nodes changes with each epoch. The amount of data allocated to storage nodes varies according to the delegated WAL tokens each epoch. Also, because participating nodes can change each epoch, there's an inevitable process of transferring slivers every time the epoch changes. Note that in the default case, slivers are transferred from the previous node to the new node directly instead of going through the recovery process. However, if there's too much data and the sliver transfer time becomes longer than the epoch, the epoch may not end. To prevent this, Walrus separates the data storage (write) and retrieval (read) processes into different epochs just before the end of an epoch. In other words, when the epoch changes and the node reconfiguration process begins, the data storage process proceeds in the next epoch from this point, while the data reading process still continues in the current epoch. When 2f+1 or more nodes in the new committee of the next epoch indicate that sliver recovery is fully prepared, the read operations also smoothly transition to the next epoch.
$WAL

• Ledger Terdesentralisasi:
Blockchain adalah buku besar terdistribusi yang dikelola oleh beberapa server. Server-server ini berbagi dan mengelola sejarah transaksi yang sama melalui algoritma konsensus. Fakta bahwa semua pihak memiliki buku besar yang sama menciptakan berbagai keunggulan blockchain, menjadikan buku besar terdistribusi sebagai inti dari teknologi blockchain. Namun, mengelola buku besar terdistribusi jauh lebih menantang dibandingkan server terpusat. Meskipun ukuran buku besar terdistribusi dapat meningkat dengan cepat, hal ini tidak menimbulkan masalah besar pada tahap awal jaringan. Namun, jika keadaan ini berlangsung terus-menerus, ketika ukuran buku besar terdistribusi menjadi sangat besar di masa depan, hambatan masuk bagi node baru yang ingin bergabung ke jaringan akan menjadi sangat tinggi, yang berpotensi menyebabkan kenaikan biaya transaksi bagi pengguna di masa depan. Oleh karena itu, sistem insentif dari sebagian besar blockchain saat ini hanya berfokus pada komputasi, bukan penyimpanan.

Seal + Walrus, kini menawarkan enkripsi dan kontrol akses bagi siapa saja yang membangun di atas protokol ini.
Sebagai lapisan data untuk Web3, @Walrus 🦭/acc sudah menyediakan infrastruktur terdesentralisasi untuk penyimpanan data, ketersediaan, dan pemrograman. Dengan peluncuran Seal, Walrus kini menawarkan solusi untuk mengintegrasikan akses data yang dapat diprogram ke dalam aplikasi apa pun dalam skala apa pun.
Teknologi penting ini mengundang para pengembang untuk memanfaatkan data publik sambil secara bersamaan melindungi informasi sensitif. Walrus bukan hanya alat, tetapi kekuatan transformasional bagi aplikasi terdesentralisasi, membuka babak menarik dalam perusahaan yang didorong oleh data.

Seiring Dusk berkembang menjadi arsitektur modular, Dusk memperkenalkan Hedger, mesin privasi baru yang dirancang khusus untuk lapisan eksekusi EVM.
Hedger membawa transaksi rahasia ke DuskEVM menggunakan kombinasi inovatif dari enkripsi homomorfik dan bukti nol pengetahuan, memungkinkan privasi siap kepatuhan untuk aplikasi keuangan dunia nyata. Berbeda dengan Zedger, yang dibangun untuk lapisan berbasis UTXO, Hedger dibangun untuk kompatibilitas penuh dengan EVM. Ini terintegrasi langsung dengan alat standar Ethereum, membuatnya skalabel, dapat diaudit, dan mudah diadopsi sejak hari pertama.

MiCA tidak hanya mengatur, tetapi juga memberikan legitimasi pada blockchain, membawa kita masuk ke dalam sistem, menetapkan persyaratan dan memberikan peluang. Penegakan MiCA membuat blockchain menjadi entitas yang jujur.
• Apa itu MiCA?
MiCA (Peraturan Pasar Aset Kripto) adalah kerangka kerja Uni Eropa untuk aset kripto. Ini dirancang untuk menyelaraskan bagaimana proyek berbasis DLT yang bukan sekuritas beroperasi, termasuk cara mereka menerbitkan aset, menyediakan layanan, mengelola penyimpanan, dan berinteraksi dengan pengguna. Dengan melakukan hal ini, jalan dibuka bagi adopsi blockchain secara massal dan institusional. Blockchain dapat dipandang seperti teknologi lainnya; lembaga-lembaga memahami cara menggunakannya, dan kerangka peraturan berarti kita dapat beroperasi secara transparan dan terbuka. MiCA memperkenalkan aturan jelas yang berlaku di seluruh Uni Eropa bagi penerbit aset kripto dan penyedia layanan. Ini menentukan bagaimana layanan harus dirancang, informasi apa yang harus diungkapkan, dan kapan aktivitas kripto memerlukan izin. MiCA melengkapi, tetapi tidak menggantikan, peraturan keuangan atau AML yang sudah ada. MiCA tidak mencakup semua hal, misalnya NFT, stablecoin algoritmik, DEX, DAO, token sekuritas, penambangan, staking, CBDC, dan protokol DeFi tanpa perantara masih berada dalam area abu-abu, tetapi MiCA menarik garis yang jelas di sekitar aktivitas yang memiliki konsekuensi peraturan.

• Apa Arti Tokenisasi bagi UKM dan Perusahaan Swasta serta bagaimana gelombang digital keuangan berikutnya memperkuat tulang punggung ekonomi.
• Keuangan Sedang Berubah. Tapi Tidak Hanya untuk Perusahaan Besar:
Selama bertahun-tahun, blockchain telah dipandang sebagai tempat bermain institusi besar dan pedagang ritel. Tetapi satu kelompok penting sering terlewat dalam diskusi ini: usaha kecil dan menengah (UKM).
Ukm membentuk lebih dari 99% semua bisnis di Uni Eropa, menyerap lebih dari 83 juta tenaga kerja dan menghasilkan lebih dari separuh PDB Eropa. Dengan kata lain, mereka adalah tulang punggung ekonomi.