Pages:
Author

Topic: [ANN][DMS] Documentchain.org | Document notarization blockchain | YescryptR32 (Read 4469 times)

legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
What could cause an error in sending a transaction to remove the masternode from the ban?
Masternode launch algorithm, please!
newbie
Activity: 33
Merit: 0
====================================
Hi,
We've added  Documentchain (DMS) to http://pool.crionic.org See below for connection details.

====================================

Fee only: 0.5% or less
BTC payouts are processed once a day for balances above 0.0015
Payouts for all other currencies are made automatically every 4 hours for balances above 0.05,
and balances more than 0.0125 are included in one of the payouts each day.

====================================
- Sample configurations -

Code for Shared:

Code:
-a yescryptR32 -o stratum+tcp://pool.crionic.org:5306 -u -p c=DMS


Exchange to BTC:
Code for Solo:

Code:
-a yescryptR32 -o stratum+tcp://pool.crionic.org:5306 -u -p c=DMS,m=solo




====================================

Support: https://discord.gg/uH9337MRYg

====================================
copper member
Activity: 142
Merit: 3
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/
copper member
Activity: 142
Merit: 3
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.
copper member
Activity: 142
Merit: 3
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
copper member
Activity: 142
Merit: 3
The masternode setup guide has been adapted to version 0.17. Deterministic Masternodes can now be deployed dialog-guided without console commands.
copper member
Activity: 142
Merit: 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
copper member
Activity: 142
Merit: 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.
copper member
Activity: 142
Merit: 3
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
copper member
Activity: 142
Merit: 3
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/
newbie
Activity: 29
Merit: 1
wow sound like great idea
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
Everything worked out, the masternode is working, I have already received the first payment.
Excellent project, I will follow the development.
copper member
Activity: 142
Merit: 3
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/
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
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?
No, she's not there. only in the tab DIP3.
first you need to run the usual, then activate the deterministic?
copper member
Activity: 142
Merit: 3
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?
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
4 days ago I launched a deterministic masternode.
Enabled status. Activation was successful.
still has not received any rewards.
here is the status of the daemon from the remote node:
Code:
./dms-cli masternode status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "185.92.151.246:41319",
  "status": "Not capable masternode: Masternode not in masternode list"

here is the status from the wallet:

Code:
masternode status
This is not a masternode (code -32603)
what's the matter?
copper member
Activity: 142
Merit: 3
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
hero member
Activity: 2146
Merit: 518
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.

Where is Harold? Who is sending replies to the internet from this account? 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.
copper member
Activity: 142
Merit: 3
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

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.
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
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/
When will Spork 15 be activated?
When all masternodes go to DIP3?
The gap between blocks can sometimes reach 30 minutes, very unevenly.
Will a more advanced difficulty adjustment mechanism be implemented?
Pages:
Jump to: