Latest posts of: Documentchain

Wichtige Information für Masternode-Betreiber

Euch ist vielleicht aufgefallen, dass seit der DIP3-Aktivierung am 10. Mai 2022 alle Masternodes enabled sind. Keine einzige ist ausgefallen.
Dies hat einen einfachen Hintergrund: in der Übergangszeit von Version 0.13 zu 0.17 werden keine Nodes bestraft, auch nicht, wenn diese offline gehen.
Mit DIP0021 "LLMQ DKG Data Sharing" wird demnächst "Proof of Service" aktiviert. Masternodes, die nicht korrekt funktionieren, werden gebannnt.

Beobachtet eure Masternodes. Wenn diese einen Pose-Score größer 0 erhalten, stimmt etwas nicht. Ab einem Score von derzeit 332 (gleich Anzahl der Masternodes) werden sie nicht weiter entlohnt. Informationen findet ihr unter https://de.documentchain.org/news/proof-of-service-bans/

Important Information for Masternode Operators

You may have noticed that since the DIP3 activation on May 10, 2022, all masternodes are enabled. Not a single one has failed.
This has a simple background: in the transition period from version 0.13 to 0.17 nodes are not sanctioned, not even if they go offline.
With DIP0021 "LLMQ DKG Data Sharing" the "Proof of Service" will be activated soon. Masternodes that do not work correctly will be banned.

Please keep an eye on your masternodes. If they get a pose score greater than 0, something is wrong. From a score of currently 332 (equal to the number of masternodes), they will not be further rewarded. Information can be found at https://documentchain.org/news/proof-of-service-bans/

Blockchain-Updates
DIP0008 (ChainLocks) wurde letzte Nacht aktiviert. Spork 17 (Quorum DKG) ist heute auf 16:00 UTC (18:00 in DE) gesetzt.
Miner voting für DIP0020 (opcodes) und DIP0021 (LLMQ DKG) startet jetzt.

DIP0008 (ChainLocks) was activated last night. Spork 17 (Quorum DKG) is set to Jun 12 2022 16:00 UTC.
Miner voting for DIP0020 (opcodes) and DIP0021 (LLMQ DKG) starts now.

DIP0008 wird bald auf der Blockchain aktiviert.
Ab Block 315530, den wir am 11. Juni gegen 20:00 UTC erwarten, werden keine Blöcke von älteren Miner mehr akzeptiert.

Führt bitte ein Update von DMS Core auf Version 0.17 "Kenji" durch, falls dies noch nicht geschehen ist.
https://de.documentchain.org/roadmap/#story-960

DIP0008 will soon be activated on Documentchain's blockchain.
Starting with block 315530, which is expected around 20:00 UTC on June 11, blocks from older miners will no longer be accepted.

Please update DMS Core to version 0.17 "Kenji" if you have not already done so.
https://documentchain.org/roadmap/#story-610

The masternode setup guide has been adapted to version 0.17. Deterministic Masternodes can now be deployed dialog-guided without console commands.

Das neue Release DMS Core 0.17 "Kenji" ist verfügbar

Dies ist ein erforderliches Upgrade, bitte die Wallets und Masternodes aktualisieren.
Neuigkeiten, Download und Anleitungen finden sich unter
https://github.com/Krekeler/documentchain/releases/tag/v0.17.0.3

New version DMS Core 0.17 "Kenji" released

This is an mandatory upgrade, please update your wallets and masternodes. Download and instructions can be found at
https://github.com/Krekeler/documentchain/releases/tag/v0.17.0.3

Documentchain's masternode system is switched to Deterministic Masternodes. Spork 15 was activated at block 308144.

Next step is the new wallet version DMS Core 0.17, a release will follow shortly.

Das neue Release DMS Core 0.13.4 "Judy" ist verfügbar.
Judy ist die Übergangsversion zwischen 0.13 und 0.17 - zwischen klassischen und deterministischen Masternodes.

Wichtige Änderungen
1. Einfache Registrierung einer deterministischen Masternode. Das Senden der Provider-Transaktion besteht aus mehreren Schritten. Dies kann jetzt mit einem einfachen Klick auf den Schalter "DIP3 Update" erledigt werden.
2. Anpassung der llmq-Werte
3. Neues testnet4
4. Neue RPC-Funktionen devgetinfo und devlistspecialtxes

Download und Anleitungen unter https://github.com/Krekeler/documentchain/releases/tag/v0.13.4.0

We are happy to announce the new DMS Core release 0.13.4 "Judy"
Judy is the mediator between version 0.13 and 0.17 - between classic and deterministic masternodes.

Notable News
1. Simple registration of a deterministic masternode. Sending the provider transaction consists of several steps. These can now be done by a simple click on "DIP3 Update" on the Masternode tab.
2. Adjustments of llmq values. Judy is the mediator between version 0.13 and 0.17 - between classical and deterministic masternodes.
3. New testnet4 deployed
4. RPC functions devgetinfo and devlistspecialtxes added

Download and instructions can be found at https://github.com/Krekeler/documentchain/releases/tag/v0.13.4.0

We are happy to announce that our new social channels are set up and already live. The social channels are managed by an agency for us to improve the marketing.
Let us spread the socials in the crypto communites and create awarness for our great project.

New Channels
Facebook: https://www.facebook.com/thedocumentchain
Instagram: https://www.instagram.com/document_chain/
LinkedIn: https://www.linkedin.com/company/documentchain/

Quote from: cryptomaxsun on November 10, 2021, 05:45:05 PM

No, she's not there. only in the tab DIP3.
first you need to run the usual, then activate the deterministic?

We are still in the transition period. You also have to activate the classic masternode,
see: https://documentchain.org/support/masternodes/

Quote from: cryptomaxsun on November 10, 2021, 03:11:42 PM

4 days ago I launched a deterministic masternode.

Code:

./dms-cli masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "185.92.151.246:41319",
"status": "Not capable masternode: Masternode not in masternode list"

}

Have you started the masternode in your local wallet on the "Masternode" tab?

Quote from: logictense on November 07, 2021, 12:18:26 PM

DIP3? I dont think its supported. Too much barking and false but zippo of sense. Will masternodes serve as repositories of knowledge, etc. the storage cells for the documents intended to be stored with DMS? I mean the documents should be stored not in the public transaction layer but in the code that is run by masternode providers.

The file hashes of the documents are stored in transactions, see https://github.com/Krekeler/documentchain/blob/master/dms-docs/document-revision-data.md

Of course, one could consider that masternodes also take on the function of cloud storage for the documents. But that would be a completely different topic and a big challenge for the masternodes. Legally, too, we would then be entering new territory.

Greetings, Harald

Quote from: cryptomaxsun on November 06, 2021, 03:24:04 PM

When will Spork 15 be activated?
When all masternodes go to DIP3?

There are still too few masternodes on DIP3. This will change with the next release, however, which will include a simple one-click-update to DIP3, see https://github.com/Krekeler/documentchain/commit/91c66145a1ac43b5442c29bf4f5bf78e3ebeaa76

Quote from: cryptomaxsun on November 06, 2021, 03:24:04 PM

The gap between blocks can sometimes reach 30 minutes, very unevenly.
Will a more advanced difficulty adjustment mechanism be implemented?

The frequent long block time is due to the Yescrypt algorithm. This can certainly be improved, but it is not really a problem.

Up-to-date information on Documentchain's DIP3 status and instructions for preparing your masternode
can now be found at https://documentchain.org/news/dip3/

DIP3 is active on mainnet (confirmed by the miners).
Please update your Masternode daemon "DMS Core" to the current version 0.13.3.1 if not already done.
https://github.com/Krekeler/documentchain/releases/tag/v0.13.3.1

The Documentchain DIP3 deployment has started, the miners must now agree. We will inform you early before the final activation via Spork 15. Masternode operators will have enough time for the update, there is no need for activity yet.