狮子王 3
1.5k Beiträge
狮子王 3
Melden
Nutzer blockieren
54 Following
1.9K+ Follower
126 Like gegeben
Beiträge
Alle
Zitierungen
·
--
Übersetzung ansehen
Fatima 5
·
--
$ETH
$BNB
guter Fund wartet auf dich
wie
Kommentare
Mitglied
$BNB
guter Fund wartet auf dich
wie
Kommentare
Mitglied
94
·
--
Übersetzung ansehen
I used to look at the Dusk bridge as a simple question of where DUSK moves.
Then I started thinking about a more important question:
What changes in the way value is represented, transferred, settled, and verified as it moves through the architecture?
DuskEVM brings EVM compatibility and Solidity-based smart contracts into the Dusk ecosystem, while DuskDS provides the settlement and data-availability foundation.
That distinction becomes interesting because Dusk supports two native transaction models.
Moonlight is public and account-based.
Phoenix is shielded and note/UTXO-based, using zero-knowledge proofs to protect transaction privacy.
So the interesting part isn't simply that Dusk has an EVM.
What caught my attention is what sits underneath that execution layer: DuskDS, where settlement, data availability, and Dusk’s native transaction models come together.
Developers get familiar EVM tooling and Solidity, while Dusk keeps its native transaction architecture for different transparency and privacy requirements.
When value moves, the deeper questions are:
What form does that value take? How is the transaction settled? What information remains visible? And where is privacy preserved?
That is what makes DuskEVM worth watching.
For me, this is more meaningful than simply saying “Dusk is EVM compatible.”
What I find more interesting is how familiar smart-contract execution interacts with Dusk’s existing settlement and transaction architecture.
The bridge may move the asset, but the architecture determines how that asset behaves along the way.
And that is the layer I would watch most closely as DuskEVM develops.
$DUSK #Dusk @Dusk_Foundation
{future}(DUSKUSDT)
I used to look at the Dusk bridge as a simple question of where DUSK moves.
Then I started thinking about a more important question:
What changes in the way value is represented, transferred, settled, and verified as it moves through the architecture?
DuskEVM brings EVM compatibility and Solidity-based smart contracts into the Dusk ecosystem, while DuskDS provides the settlement and data-availability foundation.
That distinction becomes interesting because Dusk supports two native transaction models.
Moonlight is public and account-based.
Phoenix is shielded and note/UTXO-based, using zero-knowledge proofs to protect transaction privacy.
So the interesting part isn't simply that Dusk has an EVM.
What caught my attention is what sits underneath that execution layer: DuskDS, where settlement, data availability, and Dusk’s native transaction models come together.
Developers get familiar EVM tooling and Solidity, while Dusk keeps its native transaction architecture for different transparency and privacy requirements.
When value moves, the deeper questions are:
What form does that value take? How is the transaction settled? What information remains visible? And where is privacy preserved?
That is what makes DuskEVM worth watching.
For me, this is more meaningful than simply saying “Dusk is EVM compatible.”
What I find more interesting is how familiar smart-contract execution interacts with Dusk’s existing settlement and transaction architecture.
The bridge may move the asset, but the architecture determines how that asset behaves along the way.
And that is the layer I would watch most closely as DuskEVM develops.
$DUSK #Dusk @Dusk
Then I started thinking about a more important question:
What changes in the way value is represented, transferred, settled, and verified as it moves through the architecture?
DuskEVM brings EVM compatibility and Solidity-based smart contracts into the Dusk ecosystem, while DuskDS provides the settlement and data-availability foundation.
That distinction becomes interesting because Dusk supports two native transaction models.
Moonlight is public and account-based.
Phoenix is shielded and note/UTXO-based, using zero-knowledge proofs to protect transaction privacy.
So the interesting part isn't simply that Dusk has an EVM.
What caught my attention is what sits underneath that execution layer: DuskDS, where settlement, data availability, and Dusk’s native transaction models come together.
Developers get familiar EVM tooling and Solidity, while Dusk keeps its native transaction architecture for different transparency and privacy requirements.
When value moves, the deeper questions are:
What form does that value take? How is the transaction settled? What information remains visible? And where is privacy preserved?
That is what makes DuskEVM worth watching.
For me, this is more meaningful than simply saying “Dusk is EVM compatible.”
What I find more interesting is how familiar smart-contract execution interacts with Dusk’s existing settlement and transaction architecture.
The bridge may move the asset, but the architecture determines how that asset behaves along the way.
And that is the layer I would watch most closely as DuskEVM develops.
$DUSK #Dusk @Dusk
146
·
--
Übersetzung ansehen
The first thing I noticed about Dusk finality is that a transaction doesn't simply become “done” because it appeared in a block.
There is a process happening underneath.
A provisioner proposes a block, another committee checks it, and the result moves through ratification before the network treats that state as final. With Rolling Finality, that process also accounts for what happened in the rounds before it rather than treating every block in isolation.
What I find interesting is the idea of responsibility moving through the network.
One participant puts the work forward. Others independently examine it. Then another group confirms the result. No single actor gets to decide that the state is correct simply because they produced it.
That changes how I think about “fast” settlement.
Speed is not very useful if everyone still has to wonder whether the transaction might be replaced later. Dusk is designed around deterministic finality, where a ratified block can be treated as settled rather than waiting for an ever-growing number of confirmations.
For financial applications, that distinction feels important.
The deeper idea here is not really about making blocks disappear faster. It's about turning uncertainty into coordination.
A transaction starts as a request.
It becomes shared history only after enough independent participants have checked, agreed, and moved the network forward.
That is what rolling finality means to me
{future}(DUSKUSDT)
not instant certainty, but uncertainty being steadily removed by a system that doesn't need one person to be trusted.
@Dusk_Foundation #DUSK $DUSK
The first thing I noticed about Dusk finality is that a transaction doesn't simply become “done” because it appeared in a block.
There is a process happening underneath.
A provisioner proposes a block, another committee checks it, and the result moves through ratification before the network treats that state as final. With Rolling Finality, that process also accounts for what happened in the rounds before it rather than treating every block in isolation.
What I find interesting is the idea of responsibility moving through the network.
One participant puts the work forward. Others independently examine it. Then another group confirms the result. No single actor gets to decide that the state is correct simply because they produced it.
That changes how I think about “fast” settlement.
Speed is not very useful if everyone still has to wonder whether the transaction might be replaced later. Dusk is designed around deterministic finality, where a ratified block can be treated as settled rather than waiting for an ever-growing number of confirmations.
For financial applications, that distinction feels important.
The deeper idea here is not really about making blocks disappear faster. It's about turning uncertainty into coordination.
A transaction starts as a request.
It becomes shared history only after enough independent participants have checked, agreed, and moved the network forward.
That is what rolling finality means to me
not instant certainty, but uncertainty being steadily removed by a system that doesn't need one person to be trusted.
@Dusk #DUSK $DUSK
There is a process happening underneath.
A provisioner proposes a block, another committee checks it, and the result moves through ratification before the network treats that state as final. With Rolling Finality, that process also accounts for what happened in the rounds before it rather than treating every block in isolation.
What I find interesting is the idea of responsibility moving through the network.
One participant puts the work forward. Others independently examine it. Then another group confirms the result. No single actor gets to decide that the state is correct simply because they produced it.
That changes how I think about “fast” settlement.
Speed is not very useful if everyone still has to wonder whether the transaction might be replaced later. Dusk is designed around deterministic finality, where a ratified block can be treated as settled rather than waiting for an ever-growing number of confirmations.
For financial applications, that distinction feels important.
The deeper idea here is not really about making blocks disappear faster. It's about turning uncertainty into coordination.
A transaction starts as a request.
It becomes shared history only after enough independent participants have checked, agreed, and moved the network forward.
That is what rolling finality means to me
not instant certainty, but uncertainty being steadily removed by a system that doesn't need one person to be trusted.
@Dusk #DUSK $DUSK
125
·
--
Übersetzung ansehen
I kept thinking about Dusk’s BLS12-381 implementation after seeing a small detail in the technical work: the team needed extra functionality around the curve for its own network requirements.
At first, that sounded like ordinary engineering.
But the more I looked at it, the less ordinary it felt.
BLS12-381 is an established pairing-friendly elliptic curve used in systems that rely on advanced proof and signature operations. Dusk didn’t invent the curve. It adapted the implementation so the cryptography could actually fit the way its network operates.
That distinction matters.
A lot of blockchain infrastructure gets described as if the main challenge is finding the right cryptographic primitive and plugging it into the protocol.
In practice, the harder part can come afterward.
The cryptography has to live inside an execution environment. It has to support the verification model, interact correctly with the rest of the protocol, and remain reliable under the conditions the network actually creates.
That means the boundary between “cryptography” and “protocol engineering” is thinner than it first appears.
And I think that’s the part worth paying attention to with Dusk.
The underlying mathematics still comes from an established construction. The additional work is in making that construction useful within a specific network architecture, without pretending the adaptation itself makes the cryptography magically safer.
Security still comes down to the mathematics, implementation quality, testing, and everything around it.
Maybe the next generation of blockchain infrastructure won’t be defined by inventing entirely new cryptography.
Maybe it will be defined by how well existing cryptography can be made to work inside systems that demand something more specific.
@Dusk_Foundation #DUSK $DUSK
{future}(DUSKUSDT)
I kept thinking about Dusk’s BLS12-381 implementation after seeing a small detail in the technical work: the team needed extra functionality around the curve for its own network requirements.
At first, that sounded like ordinary engineering.
But the more I looked at it, the less ordinary it felt.
BLS12-381 is an established pairing-friendly elliptic curve used in systems that rely on advanced proof and signature operations. Dusk didn’t invent the curve. It adapted the implementation so the cryptography could actually fit the way its network operates.
That distinction matters.
A lot of blockchain infrastructure gets described as if the main challenge is finding the right cryptographic primitive and plugging it into the protocol.
In practice, the harder part can come afterward.
The cryptography has to live inside an execution environment. It has to support the verification model, interact correctly with the rest of the protocol, and remain reliable under the conditions the network actually creates.
That means the boundary between “cryptography” and “protocol engineering” is thinner than it first appears.
And I think that’s the part worth paying attention to with Dusk.
The underlying mathematics still comes from an established construction. The additional work is in making that construction useful within a specific network architecture, without pretending the adaptation itself makes the cryptography magically safer.
Security still comes down to the mathematics, implementation quality, testing, and everything around it.
Maybe the next generation of blockchain infrastructure won’t be defined by inventing entirely new cryptography.
Maybe it will be defined by how well existing cryptography can be made to work inside systems that demand something more specific.
@Dusk #DUSK $DUSK
At first, that sounded like ordinary engineering.
But the more I looked at it, the less ordinary it felt.
BLS12-381 is an established pairing-friendly elliptic curve used in systems that rely on advanced proof and signature operations. Dusk didn’t invent the curve. It adapted the implementation so the cryptography could actually fit the way its network operates.
That distinction matters.
A lot of blockchain infrastructure gets described as if the main challenge is finding the right cryptographic primitive and plugging it into the protocol.
In practice, the harder part can come afterward.
The cryptography has to live inside an execution environment. It has to support the verification model, interact correctly with the rest of the protocol, and remain reliable under the conditions the network actually creates.
That means the boundary between “cryptography” and “protocol engineering” is thinner than it first appears.
And I think that’s the part worth paying attention to with Dusk.
The underlying mathematics still comes from an established construction. The additional work is in making that construction useful within a specific network architecture, without pretending the adaptation itself makes the cryptography magically safer.
Security still comes down to the mathematics, implementation quality, testing, and everything around it.
Maybe the next generation of blockchain infrastructure won’t be defined by inventing entirely new cryptography.
Maybe it will be defined by how well existing cryptography can be made to work inside systems that demand something more specific.
@Dusk #DUSK $DUSK
110
·
--
Übersetzung ansehen
I used to see Dusk’s choice of WebAssembly for smart contracts as a compatibility tradeoff.
EVM already has the developers, tooling, and familiarity. So why build around Piecrust?
The more I looked at Piecrust VM, the less I saw WASM as the point. What stood out was the kind of execution environment Dusk is trying to create.
Piecrust runs Dusk smart contracts inside a controlled WebAssembly-based VM. That means the contract isn’t just “running on a blockchain.” Its execution is being kept within rules the network can reason about consistently.
That changes how I think about the developer experience too.
You write logic, submit it, and then let the network independently execute and verify that logic. The important part isn’t who wrote the contract. It’s whether every participant can arrive at the same result under the same execution rules.
For financial infrastructure, that distinction matters.
A smart contract may eventually represent an asset, a transfer, or part of a regulated financial workflow. In that setting, predictable execution is not just a developer preference. It becomes part of the system’s reliability.
What stays with me is that Dusk didn’t choose WASM simply to be different from EVM.
Piecrust seems to reflect a deeper idea: smart-contract execution should be an environment the network can control, verify, and reproduce.
Sometimes the interesting design choice is not about adding more compatibility.
It’s about deciding what must remain predictable.
@Dusk_Foundation #Dusk $DUSK
{future}(DUSKUSDT)
I used to see Dusk’s choice of WebAssembly for smart contracts as a compatibility tradeoff.
EVM already has the developers, tooling, and familiarity. So why build around Piecrust?
The more I looked at Piecrust VM, the less I saw WASM as the point. What stood out was the kind of execution environment Dusk is trying to create.
Piecrust runs Dusk smart contracts inside a controlled WebAssembly-based VM. That means the contract isn’t just “running on a blockchain.” Its execution is being kept within rules the network can reason about consistently.
That changes how I think about the developer experience too.
You write logic, submit it, and then let the network independently execute and verify that logic. The important part isn’t who wrote the contract. It’s whether every participant can arrive at the same result under the same execution rules.
For financial infrastructure, that distinction matters.
A smart contract may eventually represent an asset, a transfer, or part of a regulated financial workflow. In that setting, predictable execution is not just a developer preference. It becomes part of the system’s reliability.
What stays with me is that Dusk didn’t choose WASM simply to be different from EVM.
Piecrust seems to reflect a deeper idea: smart-contract execution should be an environment the network can control, verify, and reproduce.
Sometimes the interesting design choice is not about adding more compatibility.
It’s about deciding what must remain predictable.
@Dusk #Dusk $DUSK
EVM already has the developers, tooling, and familiarity. So why build around Piecrust?
The more I looked at Piecrust VM, the less I saw WASM as the point. What stood out was the kind of execution environment Dusk is trying to create.
Piecrust runs Dusk smart contracts inside a controlled WebAssembly-based VM. That means the contract isn’t just “running on a blockchain.” Its execution is being kept within rules the network can reason about consistently.
That changes how I think about the developer experience too.
You write logic, submit it, and then let the network independently execute and verify that logic. The important part isn’t who wrote the contract. It’s whether every participant can arrive at the same result under the same execution rules.
For financial infrastructure, that distinction matters.
A smart contract may eventually represent an asset, a transfer, or part of a regulated financial workflow. In that setting, predictable execution is not just a developer preference. It becomes part of the system’s reliability.
What stays with me is that Dusk didn’t choose WASM simply to be different from EVM.
Piecrust seems to reflect a deeper idea: smart-contract execution should be an environment the network can control, verify, and reproduce.
Sometimes the interesting design choice is not about adding more compatibility.
It’s about deciding what must remain predictable.
@Dusk #Dusk $DUSK
1
127
·
--
Übersetzung ansehen
I initially thought Dusk was another privacy-focused L1.
Then I started digging into how it handles regulated assets, and that description stopped making much sense.
The part that caught my attention was selective privacy.
Dusk has two transaction models. Moonlight is transparent and account-based. Phoenix uses zero knowledge proofs to keep transaction details private while still proving the transaction is valid.
But Phoenix has another important feature: viewing keys.
That means private transaction data doesn't necessarily stay invisible forever. It can be selectively disclosed when an auditor, institution or compliance process actually needs access.
That's a much more practical model for regulated finance.
Institutions don't need absolute anonymity. They need sensitive information protected from the public while retaining the ability to verify what regulators or counterparties are legally required to see.
Citadel extends the same idea to identity, allowing credentials to prove specific information without exposing unnecessary personal data.
Dusk also reports €300M+ in confirmed institutional issuance, 50K+ investor reach and 210M+ DUSK staked. I treat those as project-reported figures, not independent proof of adoption.
$DUSK is where the thesis gets harder.
Network activity requires DUSK for gas, while staking secures the network. But another 500M DUSK is scheduled to enter supply over 36 years through emissions.
So I am not watching announcements anymore.
I want to see whether regulated assets actually generate sustained transactions, fees and token demand strong enough to matter against new supply.
That's when Dusk becomes more than interesting architecture.
@Dusk_Foundation #DUSK $DUSK
{future}(DUSKUSDT)
I initially thought Dusk was another privacy-focused L1.
Then I started digging into how it handles regulated assets, and that description stopped making much sense.
The part that caught my attention was selective privacy.
Dusk has two transaction models. Moonlight is transparent and account-based. Phoenix uses zero knowledge proofs to keep transaction details private while still proving the transaction is valid.
But Phoenix has another important feature: viewing keys.
That means private transaction data doesn't necessarily stay invisible forever. It can be selectively disclosed when an auditor, institution or compliance process actually needs access.
That's a much more practical model for regulated finance.
Institutions don't need absolute anonymity. They need sensitive information protected from the public while retaining the ability to verify what regulators or counterparties are legally required to see.
Citadel extends the same idea to identity, allowing credentials to prove specific information without exposing unnecessary personal data.
Dusk also reports €300M+ in confirmed institutional issuance, 50K+ investor reach and 210M+ DUSK staked. I treat those as project-reported figures, not independent proof of adoption.
$DUSK is where the thesis gets harder.
Network activity requires DUSK for gas, while staking secures the network. But another 500M DUSK is scheduled to enter supply over 36 years through emissions.
So I am not watching announcements anymore.
I want to see whether regulated assets actually generate sustained transactions, fees and token demand strong enough to matter against new supply.
That's when Dusk becomes more than interesting architecture.
@Dusk #DUSK $DUSK
Then I started digging into how it handles regulated assets, and that description stopped making much sense.
The part that caught my attention was selective privacy.
Dusk has two transaction models. Moonlight is transparent and account-based. Phoenix uses zero knowledge proofs to keep transaction details private while still proving the transaction is valid.
But Phoenix has another important feature: viewing keys.
That means private transaction data doesn't necessarily stay invisible forever. It can be selectively disclosed when an auditor, institution or compliance process actually needs access.
That's a much more practical model for regulated finance.
Institutions don't need absolute anonymity. They need sensitive information protected from the public while retaining the ability to verify what regulators or counterparties are legally required to see.
Citadel extends the same idea to identity, allowing credentials to prove specific information without exposing unnecessary personal data.
Dusk also reports €300M+ in confirmed institutional issuance, 50K+ investor reach and 210M+ DUSK staked. I treat those as project-reported figures, not independent proof of adoption.
$DUSK is where the thesis gets harder.
Network activity requires DUSK for gas, while staking secures the network. But another 500M DUSK is scheduled to enter supply over 36 years through emissions.
So I am not watching announcements anymore.
I want to see whether regulated assets actually generate sustained transactions, fees and token demand strong enough to matter against new supply.
That's when Dusk becomes more than interesting architecture.
@Dusk #DUSK $DUSK
117
·
--
Übersetzung ansehen
What happens when blockchain transparency reveals more than the market actually needs to know?
I started thinking about this differently after the Celsius bankruptcy.
When customer names and account related information became public through the court process in 2022, it showed me something simple: once sensitive financial data is exposed there’s no real way to pull it back.
On a public blockchain, that risk takes on another dimension. Financial activity can leave a permanent trail that anyone including competitors may be able to analyze.
Transparency is useful. Being able to verify what happened on-chain is one of blockchain’s biggest strengths.
But I am not sure every financial activity should be visible to everyone.
Think about a fund, bank or large investor operating on chain. Public balances, transfers and counterparties can reveal much more than transaction history. Over time they can expose relationships capital movements and even parts of a trading strategy.
That’s what made me look deeper into Dusk.
Dusk does not use one visibility model for everything. Moonlight is transparent and account based while Phoenix uses shielded transactions and zero-knowledge proofs to keep transaction details confidential while still allowing the network to verify them.
Phoenix also supports viewing keys, so information can be selectively disclosed when there’s a legitimate reason to see it.
That creates a useful middle ground: transactions can remain confidential from the wider market without making verification impossible for parties that actually need access.
Financial privacy should not mean hiding everything.
Maybe it should mean not showing everything to everyone by default.
If traditional financial activity really does move on-chain, where should we draw the line between transparency and financial privacy?
@Dusk_Foundation #Dusk $DUSK
{future}(DUSKUSDT)
What happens when blockchain transparency reveals more than the market actually needs to know?
I started thinking about this differently after the Celsius bankruptcy.
When customer names and account related information became public through the court process in 2022, it showed me something simple: once sensitive financial data is exposed there’s no real way to pull it back.
On a public blockchain, that risk takes on another dimension. Financial activity can leave a permanent trail that anyone including competitors may be able to analyze.
Transparency is useful. Being able to verify what happened on-chain is one of blockchain’s biggest strengths.
But I am not sure every financial activity should be visible to everyone.
Think about a fund, bank or large investor operating on chain. Public balances, transfers and counterparties can reveal much more than transaction history. Over time they can expose relationships capital movements and even parts of a trading strategy.
That’s what made me look deeper into Dusk.
Dusk does not use one visibility model for everything. Moonlight is transparent and account based while Phoenix uses shielded transactions and zero-knowledge proofs to keep transaction details confidential while still allowing the network to verify them.
Phoenix also supports viewing keys, so information can be selectively disclosed when there’s a legitimate reason to see it.
That creates a useful middle ground: transactions can remain confidential from the wider market without making verification impossible for parties that actually need access.
Financial privacy should not mean hiding everything.
Maybe it should mean not showing everything to everyone by default.
If traditional financial activity really does move on-chain, where should we draw the line between transparency and financial privacy?
@Dusk #Dusk $DUSK
I started thinking about this differently after the Celsius bankruptcy.
When customer names and account related information became public through the court process in 2022, it showed me something simple: once sensitive financial data is exposed there’s no real way to pull it back.
On a public blockchain, that risk takes on another dimension. Financial activity can leave a permanent trail that anyone including competitors may be able to analyze.
Transparency is useful. Being able to verify what happened on-chain is one of blockchain’s biggest strengths.
But I am not sure every financial activity should be visible to everyone.
Think about a fund, bank or large investor operating on chain. Public balances, transfers and counterparties can reveal much more than transaction history. Over time they can expose relationships capital movements and even parts of a trading strategy.
That’s what made me look deeper into Dusk.
Dusk does not use one visibility model for everything. Moonlight is transparent and account based while Phoenix uses shielded transactions and zero-knowledge proofs to keep transaction details confidential while still allowing the network to verify them.
Phoenix also supports viewing keys, so information can be selectively disclosed when there’s a legitimate reason to see it.
That creates a useful middle ground: transactions can remain confidential from the wider market without making verification impossible for parties that actually need access.
Financial privacy should not mean hiding everything.
Maybe it should mean not showing everything to everyone by default.
If traditional financial activity really does move on-chain, where should we draw the line between transparency and financial privacy?
@Dusk #Dusk $DUSK
92
·
--
Übersetzung ansehen
#dusk $DUSK @Dusk_Foundation A few days ago, Reuters reported that hackers targeted major financial firms including Blackstone, KKR, CME Group and Moody’s through social engineering.
What stayed with me was not just the attack.
It was how valuable financial information has become.
Now imagine putting sensitive financial activity on a blockchain where balances transaction amounts and transaction history can become publicly visible.
That may work for some crypto use cases. But for banks, funds and securities markets, exposing this information can create a very different problem.
That is what made me look more closely at Phoenix, Dusk’s privacy-focused UTXO model.
Phoenix uses zero-knowledge proofs to verify that a transaction follows the rules without requiring all of its sensitive details to be publicly revealed.
And that changed how I think about blockchain privacy.
The goal is not to hide everything.
The stronger idea is this:
You should be able to prove that something is valid without having to reveal everything about it.
That could matter when financial institutions need blockchain settlement but cannot publicly expose their positions transaction amounts or counterparties.
But there is still a hard question.
What happens when a regulator needs to see the information?
Privacy cannot mean nobody can ever know.
A serious financial system needs compliance, investigation and controlled access when legally required.
So for me, the interesting part of Phoenix isn't simply privacy.
It's whether blockchain can separate verification from unnecessary disclosure.
If that works at institutional scale it could change what financial blockchains are expected to expose by default.
Maybe the better question is not How transparent should blockchain be?”
It's Who actually needs to see what?
@Dusk_Foundation #DUSK $DUSK
{future}(DUSKUSDT)
#dusk $DUSK @Dusk A few days ago, Reuters reported that hackers targeted major financial firms including Blackstone, KKR, CME Group and Moody’s through social engineering.
What stayed with me was not just the attack.
It was how valuable financial information has become.
Now imagine putting sensitive financial activity on a blockchain where balances transaction amounts and transaction history can become publicly visible.
That may work for some crypto use cases. But for banks, funds and securities markets, exposing this information can create a very different problem.
That is what made me look more closely at Phoenix, Dusk’s privacy-focused UTXO model.
Phoenix uses zero-knowledge proofs to verify that a transaction follows the rules without requiring all of its sensitive details to be publicly revealed.
And that changed how I think about blockchain privacy.
The goal is not to hide everything.
The stronger idea is this:
You should be able to prove that something is valid without having to reveal everything about it.
That could matter when financial institutions need blockchain settlement but cannot publicly expose their positions transaction amounts or counterparties.
But there is still a hard question.
What happens when a regulator needs to see the information?
Privacy cannot mean nobody can ever know.
A serious financial system needs compliance, investigation and controlled access when legally required.
So for me, the interesting part of Phoenix isn't simply privacy.
It's whether blockchain can separate verification from unnecessary disclosure.
If that works at institutional scale it could change what financial blockchains are expected to expose by default.
Maybe the better question is not How transparent should blockchain be?”
It's Who actually needs to see what?
@Dusk #DUSK $DUSK
What stayed with me was not just the attack.
It was how valuable financial information has become.
Now imagine putting sensitive financial activity on a blockchain where balances transaction amounts and transaction history can become publicly visible.
That may work for some crypto use cases. But for banks, funds and securities markets, exposing this information can create a very different problem.
That is what made me look more closely at Phoenix, Dusk’s privacy-focused UTXO model.
Phoenix uses zero-knowledge proofs to verify that a transaction follows the rules without requiring all of its sensitive details to be publicly revealed.
And that changed how I think about blockchain privacy.
The goal is not to hide everything.
The stronger idea is this:
You should be able to prove that something is valid without having to reveal everything about it.
That could matter when financial institutions need blockchain settlement but cannot publicly expose their positions transaction amounts or counterparties.
But there is still a hard question.
What happens when a regulator needs to see the information?
Privacy cannot mean nobody can ever know.
A serious financial system needs compliance, investigation and controlled access when legally required.
So for me, the interesting part of Phoenix isn't simply privacy.
It's whether blockchain can separate verification from unnecessary disclosure.
If that works at institutional scale it could change what financial blockchains are expected to expose by default.
Maybe the better question is not How transparent should blockchain be?”
It's Who actually needs to see what?
@Dusk #DUSK $DUSK
1
1
1.2k
·
--
#dusk $DUSK Das Problem, Finanzdaten auf einer öffentlichen Blockchain zu setzen
Vor ein paar Jahren.
Ich dachte, die Transparenz von Blockchain sei immer eine Stärke.
Dann begann ich, die Finanzmärkte genauer zu betrachten.
Stell dir einen Fonds vor, der eine große Position bewegt.
ein Unternehmen, das sein Treasury verwaltet, oder ein Investor, der ein Wertpapier kauft – und jeder Kontotransfer sowie jede Positionsänderung wird für alle sichtbar, die der Kette zuschauen.
Das ist keine Transparenz mehr.
Das kann zu einem geschäftlichen Risiko werden.
Genau dieses Problem versucht Dusk anzugehen.
Statt jede finanzielle Transaktion vollständig öffentlich zu erzwingen, unterstützt Dusk vertrauliche Transaktionen, bei denen sensible Informationen verborgen bleiben können, während das Netzwerk dennoch verifizieren kann, dass die Transaktion gültig ist.
Sein Phoenix-Modell nutzt Zero-Knowledge-Proofs für geschützte Transfers. Ganz einfach: Das Netzwerk kann prüfen, dass sich die Transaktion an die Regeln hält, ohne den vollständigen Transaktionsinhalt für alle offenzulegen.
Informationen können außerdem gezielt offengelegt werden, wenn autorisierte Parteien sie
benötigen.
Das wird besonders interessant für Finanzwerte.
Dusk's XSC-Standard ist für vertrauliche Sicherheitsverträge ausgelegt und ermöglicht, dass tokenisierte Wertpapiere Datenschutz- und Compliance-Regeln direkt in ihre On-Chain-Workflows eingebettet haben.
Die Idee ist nicht Datenschutz statt Transparenz.
Es ist Datenschutz, wenn er gebraucht wird, und Offenlegung, wenn sie erforderlich ist.
Aber es gibt noch eine ernsthafte Frage:
Werden Finanzinstitutionen einer neuen Blockchain-Infrastruktur genug vertrauen, um echte Märkte darauf zu verlagern?
Die Technologie kann ein Datenschutzproblem lösen.
Übernahme, Regulierung, Integration und die Nutzung in der realen Welt sind jedoch viel strengere Tests.
Deshalb ist Dusk für mich interessant.
Die echte Chance könnte nicht darin liegen, Finanzwesen transparenter zu machen.
Es könnte darin liegen, Blockchain transparent zu machen, ohne jedes einzelne Stück Finanzinformation öffentlich zu machen.
Würde reguliertes Finanzwesen mit so einer selektiven Privatsphäre tatsächlich besser funktionieren?
@Dusk_Foundation #Dusk $DUSK
{future}(DUSKUSDT)
#dusk $DUSK Das Problem, Finanzdaten auf einer öffentlichen Blockchain zu setzen
Vor ein paar Jahren.
Ich dachte, die Transparenz von Blockchain sei immer eine Stärke.
Dann begann ich, die Finanzmärkte genauer zu betrachten.
Stell dir einen Fonds vor, der eine große Position bewegt.
ein Unternehmen, das sein Treasury verwaltet, oder ein Investor, der ein Wertpapier kauft – und jeder Kontotransfer sowie jede Positionsänderung wird für alle sichtbar, die der Kette zuschauen.
Das ist keine Transparenz mehr.
Das kann zu einem geschäftlichen Risiko werden.
Genau dieses Problem versucht Dusk anzugehen.
Statt jede finanzielle Transaktion vollständig öffentlich zu erzwingen, unterstützt Dusk vertrauliche Transaktionen, bei denen sensible Informationen verborgen bleiben können, während das Netzwerk dennoch verifizieren kann, dass die Transaktion gültig ist.
Sein Phoenix-Modell nutzt Zero-Knowledge-Proofs für geschützte Transfers. Ganz einfach: Das Netzwerk kann prüfen, dass sich die Transaktion an die Regeln hält, ohne den vollständigen Transaktionsinhalt für alle offenzulegen.
Informationen können außerdem gezielt offengelegt werden, wenn autorisierte Parteien sie
benötigen.
Das wird besonders interessant für Finanzwerte.
Dusk's XSC-Standard ist für vertrauliche Sicherheitsverträge ausgelegt und ermöglicht, dass tokenisierte Wertpapiere Datenschutz- und Compliance-Regeln direkt in ihre On-Chain-Workflows eingebettet haben.
Die Idee ist nicht Datenschutz statt Transparenz.
Es ist Datenschutz, wenn er gebraucht wird, und Offenlegung, wenn sie erforderlich ist.
Aber es gibt noch eine ernsthafte Frage:
Werden Finanzinstitutionen einer neuen Blockchain-Infrastruktur genug vertrauen, um echte Märkte darauf zu verlagern?
Die Technologie kann ein Datenschutzproblem lösen.
Übernahme, Regulierung, Integration und die Nutzung in der realen Welt sind jedoch viel strengere Tests.
Deshalb ist Dusk für mich interessant.
Die echte Chance könnte nicht darin liegen, Finanzwesen transparenter zu machen.
Es könnte darin liegen, Blockchain transparent zu machen, ohne jedes einzelne Stück Finanzinformation öffentlich zu machen.
Würde reguliertes Finanzwesen mit so einer selektiven Privatsphäre tatsächlich besser funktionieren?
@Dusk #Dusk $DUSK
Vor ein paar Jahren.
Ich dachte, die Transparenz von Blockchain sei immer eine Stärke.
Dann begann ich, die Finanzmärkte genauer zu betrachten.
Stell dir einen Fonds vor, der eine große Position bewegt.
ein Unternehmen, das sein Treasury verwaltet, oder ein Investor, der ein Wertpapier kauft – und jeder Kontotransfer sowie jede Positionsänderung wird für alle sichtbar, die der Kette zuschauen.
Das ist keine Transparenz mehr.
Das kann zu einem geschäftlichen Risiko werden.
Genau dieses Problem versucht Dusk anzugehen.
Statt jede finanzielle Transaktion vollständig öffentlich zu erzwingen, unterstützt Dusk vertrauliche Transaktionen, bei denen sensible Informationen verborgen bleiben können, während das Netzwerk dennoch verifizieren kann, dass die Transaktion gültig ist.
Sein Phoenix-Modell nutzt Zero-Knowledge-Proofs für geschützte Transfers. Ganz einfach: Das Netzwerk kann prüfen, dass sich die Transaktion an die Regeln hält, ohne den vollständigen Transaktionsinhalt für alle offenzulegen.
Informationen können außerdem gezielt offengelegt werden, wenn autorisierte Parteien sie
benötigen.
Das wird besonders interessant für Finanzwerte.
Dusk's XSC-Standard ist für vertrauliche Sicherheitsverträge ausgelegt und ermöglicht, dass tokenisierte Wertpapiere Datenschutz- und Compliance-Regeln direkt in ihre On-Chain-Workflows eingebettet haben.
Die Idee ist nicht Datenschutz statt Transparenz.
Es ist Datenschutz, wenn er gebraucht wird, und Offenlegung, wenn sie erforderlich ist.
Aber es gibt noch eine ernsthafte Frage:
Werden Finanzinstitutionen einer neuen Blockchain-Infrastruktur genug vertrauen, um echte Märkte darauf zu verlagern?
Die Technologie kann ein Datenschutzproblem lösen.
Übernahme, Regulierung, Integration und die Nutzung in der realen Welt sind jedoch viel strengere Tests.
Deshalb ist Dusk für mich interessant.
Die echte Chance könnte nicht darin liegen, Finanzwesen transparenter zu machen.
Es könnte darin liegen, Blockchain transparent zu machen, ohne jedes einzelne Stück Finanzinformation öffentlich zu machen.
Würde reguliertes Finanzwesen mit so einer selektiven Privatsphäre tatsächlich besser funktionieren?
@Dusk #Dusk $DUSK
1
1
4.9k
·
--
Übersetzung ansehen
#dusk $DUSK A few days ago, Reuters reported that hackers targeted major financial firms, including Blackstone, KKR, CME Group and Moody’s. The attackers used simple social engineering to go after sensitive access and financial information.
It made me think about a different problem in finance.
We usually talk about blockchain transparency as a strength. But what if every balance, position, counterparty and transaction was visible to everyone?
@For a normal crypto user, that may be acceptable.
For a bank, fund or financial institution, it can become a serious problem.
I used to think privacy and blockchain transparency were simply opposites. But researching Dusk changed how I look at it.
Dusk is building a Layer-1 around regulated finance, where sensitive information can stay confidential while selected information can still be disclosed for audits or compliance. Its XSC standard is designed for confidential smart contracts and tokenized securities.
The interesting part is not “privacy.”
It is selective privacy.
A regulator may need proof that a transaction follows the rules. A competitor does not need to know the size of your position.
That sounds practical.
But there is still a hard question: can confidential blockchain infrastructure deliver the privacy institutions need without making compliance and oversight harder?
That, to me, is the real test for Dusk.
Would financial markets actually use public blockchain infrastructure if privacy could be built into the system from the start?
@Dusk_Foundation #DUSK $DUSK
{future}(DUSKUSDT)
#dusk $DUSK A few days ago, Reuters reported that hackers targeted major financial firms, including Blackstone, KKR, CME Group and Moody’s. The attackers used simple social engineering to go after sensitive access and financial information.
It made me think about a different problem in finance.
We usually talk about blockchain transparency as a strength. But what if every balance, position, counterparty and transaction was visible to everyone?
@For a normal crypto user, that may be acceptable.
For a bank, fund or financial institution, it can become a serious problem.
I used to think privacy and blockchain transparency were simply opposites. But researching Dusk changed how I look at it.
Dusk is building a Layer-1 around regulated finance, where sensitive information can stay confidential while selected information can still be disclosed for audits or compliance. Its XSC standard is designed for confidential smart contracts and tokenized securities.
The interesting part is not “privacy.”
It is selective privacy.
A regulator may need proof that a transaction follows the rules. A competitor does not need to know the size of your position.
That sounds practical.
But there is still a hard question: can confidential blockchain infrastructure deliver the privacy institutions need without making compliance and oversight harder?
That, to me, is the real test for Dusk.
Would financial markets actually use public blockchain infrastructure if privacy could be built into the system from the start?
@Dusk #DUSK $DUSK
It made me think about a different problem in finance.
We usually talk about blockchain transparency as a strength. But what if every balance, position, counterparty and transaction was visible to everyone?
@For a normal crypto user, that may be acceptable.
For a bank, fund or financial institution, it can become a serious problem.
I used to think privacy and blockchain transparency were simply opposites. But researching Dusk changed how I look at it.
Dusk is building a Layer-1 around regulated finance, where sensitive information can stay confidential while selected information can still be disclosed for audits or compliance. Its XSC standard is designed for confidential smart contracts and tokenized securities.
The interesting part is not “privacy.”
It is selective privacy.
A regulator may need proof that a transaction follows the rules. A competitor does not need to know the size of your position.
That sounds practical.
But there is still a hard question: can confidential blockchain infrastructure deliver the privacy institutions need without making compliance and oversight harder?
That, to me, is the real test for Dusk.
Would financial markets actually use public blockchain infrastructure if privacy could be built into the system from the start?
@Dusk #DUSK $DUSK
5
2
167
·
--
@Square-Creator-ce2378404 #BNB $BNB 📈 BNB/USDT Intraday-Signal
Richtung: 🟢 KAUF
Einstieg: $592–596
Take Profit 1: $605
Take Profit 2: $615
Take Profit 3: $625
Stop Loss: $583 (unter dem wichtigen Support)
Handelsidee: BNB hält sich um die wichtige $592-Unterstützung. Wenn Käufer dieses Niveau verteidigen, liegt der nächste Widerstand bei etwa $605, mit Upside-Potenzial Richtung $615–625. Ein klarer Break unter $583 würde das bullische Setup ungültig machen.
Risiko: Verwende eine korrekte Positionsgröße und riskiere nicht mehr als 1–2% deines Trading-Kapitals bei einem einzelnen Trade.
{future}(BNBUSDT)
@BNB #BNB $BNB 📈 BNB/USDT Intraday-Signal
Richtung: 🟢 KAUF
Einstieg: $592–596
Take Profit 1: $605
Take Profit 2: $615
Take Profit 3: $625
Stop Loss: $583 (unter dem wichtigen Support)
Handelsidee: BNB hält sich um die wichtige $592-Unterstützung. Wenn Käufer dieses Niveau verteidigen, liegt der nächste Widerstand bei etwa $605, mit Upside-Potenzial Richtung $615–625. Ein klarer Break unter $583 würde das bullische Setup ungültig machen.
Risiko: Verwende eine korrekte Positionsgröße und riskiere nicht mehr als 1–2% deines Trading-Kapitals bei einem einzelnen Trade.
Richtung: 🟢 KAUF
Einstieg: $592–596
Take Profit 1: $605
Take Profit 2: $615
Take Profit 3: $625
Stop Loss: $583 (unter dem wichtigen Support)
Handelsidee: BNB hält sich um die wichtige $592-Unterstützung. Wenn Käufer dieses Niveau verteidigen, liegt der nächste Widerstand bei etwa $605, mit Upside-Potenzial Richtung $615–625. Ein klarer Break unter $583 würde das bullische Setup ungültig machen.
Risiko: Verwende eine korrekte Positionsgröße und riskiere nicht mehr als 1–2% deines Trading-Kapitals bei einem einzelnen Trade.
68
·
--
@Square-Creator-810195574 #sol $SOL
🟢 SOL/USDT – LONG Signal (Hohes Risiko)
Einstieg: $72.80 – $73.60
Take Profit 1: $75.50
Take Profit 2: $77.80
Take Profit 3: $80.00
Stop Loss: $70.80
Handelsplan
✅ Nur innerhalb der Einstiegzone einsteigen.
✅ Teilgewinne bei jedem TP mitnehmen.
✅ Stop Loss nach TP1 auf Break-even setzen, um das Risiko zu reduzieren.
Risiko: 1–2% deines Trading-Kapitals pro Trade.
{future}(SOLUSDT)
@soL #sol $SOL
🟢 SOL/USDT – LONG Signal (Hohes Risiko)
Einstieg: $72.80 – $73.60
Take Profit 1: $75.50
Take Profit 2: $77.80
Take Profit 3: $80.00
Stop Loss: $70.80
Handelsplan
✅ Nur innerhalb der Einstiegzone einsteigen.
✅ Teilgewinne bei jedem TP mitnehmen.
✅ Stop Loss nach TP1 auf Break-even setzen, um das Risiko zu reduzieren.
Risiko: 1–2% deines Trading-Kapitals pro Trade.
🟢 SOL/USDT – LONG Signal (Hohes Risiko)
Einstieg: $72.80 – $73.60
Take Profit 1: $75.50
Take Profit 2: $77.80
Take Profit 3: $80.00
Stop Loss: $70.80
Handelsplan
✅ Nur innerhalb der Einstiegzone einsteigen.
✅ Teilgewinne bei jedem TP mitnehmen.
✅ Stop Loss nach TP1 auf Break-even setzen, um das Risiko zu reduzieren.
Risiko: 1–2% deines Trading-Kapitals pro Trade.
76
·
--
@Square-Creator-1d1b19f0b09ed #ETH $ETH ETH handelt bei etwa **$1.870–$1.915**, im letzten 24-Stunden-Zeitraum ungefähr 1–2% im Plus, aber über die vergangene Woche leicht im Minus (~-0,7%) — insgesamt eher seitwärts/konsolidierend und deutlich unter seinem Allzeithoch von ~$4.946.
Kurzer Überblick:
- Preis: ~$1.900 (leicht je nach Börse unterschiedlich)
- Marktkapitalisierung: ~$229B (#2 nach Marktkapitalisierung)
- 24h-Volumen: ~$8–9B
Falls du mit „Signal“ etwas konkreter meinst — ein Trading-Indikator (RSI, MACD), On-Chain-Aktivität oder News-Stimmung — sag Bescheid, dann kann ich das alternativ genauer unter die Lupe nehmen.
@ETH- #ETH $ETH ETH handelt bei etwa **$1.870–$1.915**, im letzten 24-Stunden-Zeitraum ungefähr 1–2% im Plus, aber über die vergangene Woche leicht im Minus (~-0,7%) — insgesamt eher seitwärts/konsolidierend und deutlich unter seinem Allzeithoch von ~$4.946.
Kurzer Überblick:
- Preis: ~$1.900 (leicht je nach Börse unterschiedlich)
- Marktkapitalisierung: ~$229B (#2 nach Marktkapitalisierung)
- 24h-Volumen: ~$8–9B
Falls du mit „Signal“ etwas konkreter meinst — ein Trading-Indikator (RSI, MACD), On-Chain-Aktivität oder News-Stimmung — sag Bescheid, dann kann ich das alternativ genauer unter die Lupe nehmen.
Kurzer Überblick:
- Preis: ~$1.900 (leicht je nach Börse unterschiedlich)
- Marktkapitalisierung: ~$229B (#2 nach Marktkapitalisierung)
- 24h-Volumen: ~$8–9B
Falls du mit „Signal“ etwas konkreter meinst — ein Trading-Indikator (RSI, MACD), On-Chain-Aktivität oder News-Stimmung — sag Bescheid, dann kann ich das alternativ genauer unter die Lupe nehmen.
94
·
--
@Square-Creator-a6b19761fc5e5 #BTC $BTC Auf Grundlage des aktuellen Marktes handelt BTC bei etwa 63.000 bis 64.000 US-Dollar.
Lernen-/Handels-Setup (keine Finanzberatung):
🟢 LONG BTC
Einstieg: 63.300–63.600 US-Dollar
TP1: 64.500 US-Dollar
TP2: 65.500 US-Dollar
TP3: 66.800 US-Dollar
SL: 62.700 US-Dollar
Risikomanagement:
Riskiere nur 1–2 % deines Handelskapitals bei einem einzelnen Trade.
Verlege deinen Stop-Loss nach TP1 auf Break-even, falls sich der Trade zu deinen Gunsten entwickelt.
Wenn du Binance Futures handelst, sag mir bitte deine bevorzugte Zeiteinheit (15m, 1H oder 4H) und ob du mit 5×, 10× oder 20× Hebel handelst, dann passe ich das Setup entsprechend an.
{future}(BTCUSDT)
@BTC #BTC $BTC Auf Grundlage des aktuellen Marktes handelt BTC bei etwa 63.000 bis 64.000 US-Dollar.
Lernen-/Handels-Setup (keine Finanzberatung):
🟢 LONG BTC
Einstieg: 63.300–63.600 US-Dollar
TP1: 64.500 US-Dollar
TP2: 65.500 US-Dollar
TP3: 66.800 US-Dollar
SL: 62.700 US-Dollar
Risikomanagement:
Riskiere nur 1–2 % deines Handelskapitals bei einem einzelnen Trade.
Verlege deinen Stop-Loss nach TP1 auf Break-even, falls sich der Trade zu deinen Gunsten entwickelt.
Wenn du Binance Futures handelst, sag mir bitte deine bevorzugte Zeiteinheit (15m, 1H oder 4H) und ob du mit 5×, 10× oder 20× Hebel handelst, dann passe ich das Setup entsprechend an.
Lernen-/Handels-Setup (keine Finanzberatung):
🟢 LONG BTC
Einstieg: 63.300–63.600 US-Dollar
TP1: 64.500 US-Dollar
TP2: 65.500 US-Dollar
TP3: 66.800 US-Dollar
SL: 62.700 US-Dollar
Risikomanagement:
Riskiere nur 1–2 % deines Handelskapitals bei einem einzelnen Trade.
Verlege deinen Stop-Loss nach TP1 auf Break-even, falls sich der Trade zu deinen Gunsten entwickelt.
Wenn du Binance Futures handelst, sag mir bitte deine bevorzugte Zeiteinheit (15m, 1H oder 4H) und ob du mit 5×, 10× oder 20× Hebel handelst, dann passe ich das Setup entsprechend an.
1.6k
6
107
1.6k
·
--
GUT
GUT
J I L A N I
·
--
Die Entwicklungsaussichten für Solana
🔴 Der Bereich um 183,60 $ wird ein wichtiger Niveau sein, das es zu beobachten gilt. Nach den Prinzipien des harmonischen Handels fungiert dieser Bereich oft als Umkehrzone, wo Verkäufer in den Markt zurückkehren können. Sollte es Solana jedoch gelingen, diese Marke mit starkem Volumen und Momentum zu überschreiten, könnte sich der Aufwärtstrend fortsetzen und auf eine vollständige Rückkehr zu 187,52 $ – seinem jüngsten Hoch – abzielen. Dieser Anstieg würde einen Gewinn von etwa 5,60 % im Vergleich zu den aktuellen Preisen darstellen.
Im Gegensatz dazu könnte es, wenn SOL Schwierigkeiten hat, die 183,60 $ zu überschreiten, ein Signal für eine Erschöpfung des Aufwärtsmomentums sein. In diesem Fall könnte der Token einige Gewinnmitnahmen erfahren, bevor er einen weiteren Fortschritt versucht.
Im Gegensatz dazu könnte es, wenn SOL Schwierigkeiten hat, die 183,60 $ zu überschreiten, ein Signal für eine Erschöpfung des Aufwärtsmomentums sein. In diesem Fall könnte der Token einige Gewinnmitnahmen erfahren, bevor er einen weiteren Fortschritt versucht.
·
--
Xai
Xai
合约涨跌AI预判-VIP-0907版
·
--
@XAI_GAMES Xai Entwickler-Ökosystem-Empowerment
Xai bietet nicht nur Spielern ein neues Unterhaltungserlebnis, sondern auch Spieleentwicklern eine offene, niedrigschwellige Innovationsplattform. Entwickler können das Xai-Ökosystem nutzen, um problemlos auf die Blockchain zu gehen, Spiele zu veröffentlichen und einzigartige Belohnungsmechanismen zu integrieren, um eine nahtlose Verbindung zwischen traditionellen Spielen und Blockchain-Technologie zu erreichen. Die umfassende technische Unterstützung und transparente Anreize der Plattform machen es einfach, kreative Ideen zu monetarisieren, wodurch mehr hochwertige Projekte entstehen und die Innovation der digitalen Unterhaltungsindustrie gemeinsam vorangetrieben wird.
$XAI
Xai bietet nicht nur Spielern ein neues Unterhaltungserlebnis, sondern auch Spieleentwicklern eine offene, niedrigschwellige Innovationsplattform. Entwickler können das Xai-Ökosystem nutzen, um problemlos auf die Blockchain zu gehen, Spiele zu veröffentlichen und einzigartige Belohnungsmechanismen zu integrieren, um eine nahtlose Verbindung zwischen traditionellen Spielen und Blockchain-Technologie zu erreichen. Die umfassende technische Unterstützung und transparente Anreize der Plattform machen es einfach, kreative Ideen zu monetarisieren, wodurch mehr hochwertige Projekte entstehen und die Innovation der digitalen Unterhaltungsindustrie gemeinsam vorangetrieben wird.
$XAI
·
--
👻👻👻
👻👻👻
Sarah Suleiman
·
--
Strategie kauft 4.020 BTC Bitcoin für 427 Millionen Dollar, Gesamtbestände erreichen 580.250 BTC
Strategie (ehemals MicroStrategy), ein Bitcoin-
BTC +2,20%
Treasury-Unternehmen, das von dem amerikanischen Unternehmer und Investor Michael Saylor mitbegründet wurde, kaufte letzte Woche 4.020 Bitcoins für etwa 427,1 Millionen Dollar zu einem Durchschnittspreis von 106.237 Dollar pro Coin, wie in einer am Montag veröffentlichten Pressemitteilung mitgeteilt wurde.
Durch den Erwerb stiegen die Gesamtbestände von Strategie auf 580.250 BTC, die zusammen etwa 40,61 Milliarden Dollar gekostet haben, bei einem Durchschnittspreis von 69.979 Dollar pro Bitcoin, einschließlich Gebühren und Ausgaben. Das Unternehmen verzeichnet Papiervorteile in Höhe von 22,7 Milliarden Dollar und kontrolliert fast 3 % des gesamten Bitcoin-Angebots von 21 Millionen.
Strategie finanzierte die neuesten Käufe mit Erlösen aus dem Verkauf ihrer Stammaktien der Klasse A, MSTR, der perpetual strike Vorzugsaktien, STRK, und der Series A perpetual strife Vorzugsaktien, STRF. Zwischen dem 19. Mai und dem 23. Mai verkaufte Strategie 847.000 MSTR-Aktien für 348,7 Millionen Dollar Nettoprofit. Außerdem verkaufte Strategie 678.970 STRK-Aktien für 67,9 Millionen Dollar und 104.423 STRF-Aktien für 10,4 Millionen Dollar Nettoprofit.
Bernstein prognostiziert 330 Milliarden Dollar von Strategiekopien
Mehr Institutionen haben das Spielbuch der Strategie übernommen und Bitcoin-Reserven in irgendeiner Form eingerichtet. Über 70 Unternehmen haben BTC in ihren Bilanzen bestätigt, wobei Unternehmen wie Tether-unterstützte Twenty One KURL, Metaplanet und Semler Scientific im Wettbewerb um den Bitcoin-Akkumulationskampf beigetreten sind.$BTC
$XRP
$SOL
Strategie (ehemals MicroStrategy), ein Bitcoin-
BTC +2,20%
Treasury-Unternehmen, das von dem amerikanischen Unternehmer und Investor Michael Saylor mitbegründet wurde, kaufte letzte Woche 4.020 Bitcoins für etwa 427,1 Millionen Dollar zu einem Durchschnittspreis von 106.237 Dollar pro Coin, wie in einer am Montag veröffentlichten Pressemitteilung mitgeteilt wurde.
Durch den Erwerb stiegen die Gesamtbestände von Strategie auf 580.250 BTC, die zusammen etwa 40,61 Milliarden Dollar gekostet haben, bei einem Durchschnittspreis von 69.979 Dollar pro Bitcoin, einschließlich Gebühren und Ausgaben. Das Unternehmen verzeichnet Papiervorteile in Höhe von 22,7 Milliarden Dollar und kontrolliert fast 3 % des gesamten Bitcoin-Angebots von 21 Millionen.
Strategie finanzierte die neuesten Käufe mit Erlösen aus dem Verkauf ihrer Stammaktien der Klasse A, MSTR, der perpetual strike Vorzugsaktien, STRK, und der Series A perpetual strife Vorzugsaktien, STRF. Zwischen dem 19. Mai und dem 23. Mai verkaufte Strategie 847.000 MSTR-Aktien für 348,7 Millionen Dollar Nettoprofit. Außerdem verkaufte Strategie 678.970 STRK-Aktien für 67,9 Millionen Dollar und 104.423 STRF-Aktien für 10,4 Millionen Dollar Nettoprofit.
Bernstein prognostiziert 330 Milliarden Dollar von Strategiekopien
Mehr Institutionen haben das Spielbuch der Strategie übernommen und Bitcoin-Reserven in irgendeiner Form eingerichtet. Über 70 Unternehmen haben BTC in ihren Bilanzen bestätigt, wobei Unternehmen wie Tether-unterstützte Twenty One KURL, Metaplanet und Semler Scientific im Wettbewerb um den Bitcoin-Akkumulationskampf beigetreten sind.$BTC
$XRP
$SOL
Anmelden und weiter Inhalte entdecken
Krypto-Nutzer weltweit auf Binance Square kennenlernen
⚡️ Bleib in Sachen Krypto stets am Puls.
💬 Die weltgrößte Kryptobörse vertraut darauf.
👍 Erhalte verlässliche Einblicke von verifizierten Creators.
E-Mail-Adresse/Telefonnummer
Trendthemen
CPIWatch
86.6M Aufrufe
501,964 Kommentare
Teile & gewinne Traffic-Belohnungen in unserer Kampagne mit den Trend-Hashtags
✨Thema: Wird CPI eine Zinserhöhung auslösen?
👉So nimmst du teil:
Veröffentliche einen kurzen Beitrag oder Artikel mit dem Hashtag #CPIWatch
Erstelle Inhalte basierend auf den folgenden zwei Blickwinkeln:
- Nichtlandwirtschaftliche Payrolls übertreffen die Erwartungen und CPI steht kurz bevor—glaubst du, dass die Fed die Zinsen erhöht oder hält?
- Bärisch oder bullisch? Teile deine Einschätzung und präsentiere deine Aktien oder Gold-Trades/Bestände mit unserem Widget zum Teilen von Trades.
🚀Kampagnenzeitraum:
- 2026-09-11 3:00 - 2026-09-12 9:00 UTC
🎁Belohnung:
- Qualifizierte Beiträge, die die oben genannten Richtlinien einhalten und mehr als 100 Wörter enthalten, werden überprüft und können möglicherweise einen zufälligen Traffic-Boost von 500 bis 3.000 Views erhalten. Du erhältst eine Benachrichtigung von deiner Feed-Sekretärin, wenn dein Beitrag ausgewählt wurde.
- Erhalte die Chance, dass dein Artikel auf Binance Square Official vorgestellt wird
Brauchst du Ideen für deinen Beitrag? Besuche die Themen-Seite #CPIWatch oder die Square Guide on How to Post for Better Reach.
Binance Square Official
·487 Likes
·1.1M Aufrufe
BitcoinReboundsAbove$79KAfterCPI
306 Aufrufe
60 Kommentare
BNBTops730USDT
4,046 Aufrufe
367 Kommentare