Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)
Pages:
Author

Topic: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control] - page 6. (Read 8135 times)

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
November 04, 2019, 03:08:41 AM
#77
 
 Upcoming changes ...

Often there are situations in which a chain of blocks with a later timestamp but with greater trust replaces the earlier found blocks.
I do not like such situations, and I consider this vulnerability. In the updated code, a chain of blocks with a larger time stamp loses its trust.
Code ...
Code:
CBlockIndex* pblockindex = NULL;
    int nPossibleHeight = pindexNew->pprev->nHeight + 1;
    if (fDebug)
        printf(" 'AddToBlockIndex()' - The new block pretends to a height %d, block chain height %d\n", nPossibleHeight,
               pindexBest->nHeight);

    if (nPossibleHeight < pindexBest->nHeight && fHardForkOne)
    {
        if (nPossibleHeight <= pindexBest->nHeight - nTriggerDepth)
        {
            if (fDebug)
                printf(" 'AddToBlockIndex()' - The new block pretends to a height %d, maximum allowed block height for a competing chain %d\n", nPossibleHeight,
                pindexBest->nHeight - nTriggerDepth);
            pindexNew->bnChainTrust = 0;

        }

        pblockindex = FindBlockByHeight(nPossibleHeight);
        if (pindexNew->GetBlockTime() > pblockindex->GetBlockTime())
        {
            if (fDebug)
                printf(" 'AddToBlockIndex()' - Generation time of a new block date=%s later than available in the database date=%s\n",
                DateTimeStrFormat("%x %H:%M:%S", pindexNew->GetBlockTime()).c_str(), DateTimeStrFormat("%x %H:%M:%S",
                pblockindex->GetBlockTime()).c_str());
            pindexNew->bnChainTrust = 0;
        }
        else if (pindexNew->GetBlockTime() < pblockindex->GetBlockTime())
        {
                 if (nPossibleHeight < pindexBest->nHeight && nPossibleHeight > pindexBest->nHeight - nTriggerDepth)
                 {
                     if (fDebug)
                         printf(" 'AddToBlockIndex()' - The generation time of a new block date=%s earlier than the one in the database date=%s\n",
                         DateTimeStrFormat("%x %H:%M:%S", pindexNew->GetBlockTime()).c_str(), DateTimeStrFormat("%x %H:%M:%S",
                         pblockindex->GetBlockTime()).c_str());
                     bnBestChainTrust = pblockindex->pprev->bnChainTrust;
                 }
        }
    }

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
October 30, 2019, 12:09:12 PM
#76
 Upcoming changes ...

2) If the "ChainTrust" matches, the network will not wait for the child block from the competitor’s node. Code..

Code:
// New best
    if (pindexNew->bnChainTrust > bnBestChainTrust)
    {
        if (!SetBestChain(state, txdb, pindexNew))
            return false;
    }
    else if (pindexNew->bnChainTrust == bnBestChainTrust && fHardForkOne && pindexPrevPos->GetBlockHash() >=
        pindexPrevPrevPos->GetBlockHash())
    {
        printf(" 'CBlock' - BestChainTrust %s\n", bnBestChainTrust.ToString().c_str());
        printf(" 'CBlock' - NewChainTrust %s\n", pindexNew->bnChainTrust.ToString().c_str());
        if (((pindexNew->IsProofOfStake() && pindexBest->IsProofOfStake()) ? (pindexNew->GetBlockHash() >
            pindexBest->GetBlockHash()) : (hash > pindexBest->GetBlockHash())) ||
            (pindexBest->IsProofOfWork() && pindexNew->IsProofOfStake()))
        {
            printf(" 'CBlock' bnChainTrust = bnBestChainTrust - Block accepted\n");
            if (!SetBestChain(state, txdb, pindexNew))
            {
                return false;
            }
        }
        else
        {
             printf(" 'CBlock' bnChainTrust = bnBestChainTrust - Block not accepted\n");
             return false;
        }
    }
    else if (pindexNew->bnChainTrust == bnBestChainTrust && fHardForkOne && pindexPrevPos->GetBlockHash() <
             pindexPrevPrevPos->GetBlockHash())
    {
        printf(" 'CBlock_' - BestChainTrust %s\n", bnBestChainTrust.ToString().c_str());
        printf(" 'CBlock_' - NewChainTrust %s\n", pindexNew->bnChainTrust.ToString().c_str());
        if (((pindexNew->IsProofOfStake() && pindexBest->IsProofOfStake()) ? (pindexNew->GetBlockHash() <
            pindexBest->GetBlockHash()) : (hash < pindexBest->GetBlockHash())) ||
            (pindexBest->IsProofOfWork() && pindexNew->IsProofOfStake()))
        {
            printf(" 'CBlock' bnChainTrust = bnBestChainTrust - Block accepted\n");
            if (!SetBestChain(state, txdb, pindexNew))
            {
                return false;
            }
        }
        else
        {
             printf(" 'CBlock' bnChainTrust = bnBestChainTrust - Block not accepted\n");
             return false;
        }
    }
    txdb.Close();


Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
October 29, 2019, 05:38:14 AM
#75

  Upcoming changes ...

1) Adaptation of difficulty for NF19 - 20 / min = 0.00024 -> 0.00000096 /

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
June 09, 2019, 09:25:15 AM
#74
  
  To enable the function "setcontrolrealtime", you must specify the parameter "setcontrolrealtime=1".
This function changes the limit on the number of transmitted blocks. In the case when the sent "inv"
has one size, and the received "getdata" the other limit is set to 10. Additionally, when transferring
blocks with a height of more than 150000, the limit is set to 30.
  Starting from the previous version, in the event of a socket error, the transfer of a chain of blocks is
interrupted on the block with an error.

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
June 09, 2019, 09:04:42 AM
#73

New version available

CACHE-Project, Changing the parameters of the "setcontrolrealtime" function. Implemented stop the transfer of a chain of blocks in case of a socket error

Version : v_6.1.1.30
Version of git : v_0.7.5.149
Subversion : v_0.7.6.42


Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
June 05, 2019, 10:37:06 AM
#72

  Fixed balance calculation errors. Added new features for analyzing addresses and wallet accounts.
New features -

"fixerrorgetbalancefunction"
"getaddressbalance"
"getbalancealladdresses"
"getbasebalancealladdresses"
"getreceivedbyalladdresses"
"getsenttobyalladdresses"
"getstakebalancealladdresses"

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
June 05, 2019, 10:12:41 AM
#71
New version available

CACHE-Project, Adding new features and correcting errors in the balance calculation

Version : v_6.1.1.29
Version of git : v_0.7.5.147
Subversion : v_0.7.6.41


Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 30, 2019, 08:56:12 AM
#70

  Work function "setreconnectpresenttime" - log.

Code:
trying connection 188.163.45.132:2225 lastseen=331,3hrs
     For a long time without new blocks - queue: 0 loops from: max
disconnecting node 185.220.101.26:35056
     Start block sync

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 30, 2019, 12:31:54 AM
#69
 
  Job the filter - log ..

Code:
accepted connection 167.86.103.109:53424
disconnecting node 167.86.103.109:53424
accepted connection 167.86.103.109:53443
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 1
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 1
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 2
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 3
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 4
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 5
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 6
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 7
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 8
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 9
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 10
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 11
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 12
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 13
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 14
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 15
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 16
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 17
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 18
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 19
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 20
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 21
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 22
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 23
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 24
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 25
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 26
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 27
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 28
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 29
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 30
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 31
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 32
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 33
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 34
disconnecting node 167.86.103.109:53443
accepted connection 167.86.103.109:53654
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 35
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 36
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 37
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 38
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 39
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 40
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 41
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 42
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 43
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 44
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 45
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 46
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 47
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 48
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 49
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 50
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 51
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 52
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 53
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 54
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 55
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 56
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 57
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 58
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 59
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 60
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 61
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 62
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 63
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 64
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 65
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 66
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 67
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 68
socket closed
disconnecting node 167.86.103.109:53654
accepted connection 167.86.103.109:53810
disconnecting node 167.86.103.109:53810
accepted connection 167.86.103.109:53814
disconnecting node 167.86.103.109:53814
accepted connection 167.86.103.109:53816
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 69
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 70
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 71
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 72
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 73
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 74
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 75
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 76
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 77
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 78
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 79
  ProcessMessages - !msg.complete(): 167.86.103.109 - error count: 80
  ProcessMessages - spam ip actual: 167.86.103.109
disconnecting node 167.86.103.109:53816
connection from 167.86.103.109:53882 dropped (IsGlobalIpBanned)

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 20, 2019, 11:23:08 PM
#68
 
 These additions are implemented to eliminate the possibility of repeated use of the same coins. This is exactly what happened on the Cryptopia Exchange. For double spending, coins with a small number of connections and a small network hash rate or POS coins were chosen. Moreover, an attack of 51% is not obligatory, it is enough to tear off the exchange's wallet from its main network. Coins with which this focus was repeated many times and were delist from the Cryptopia.

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 20, 2019, 11:30:37 AM
#67

 New settings and what they are for.

 Options - ("setreload" "setreconnecting") - used when synchronizing blocks.

1) default
Synchronization mode with disconnection from peers sending incorrect data.

setreload=0
setreconnecting=1

2)
Use in cases where some members of the network are not interested in the presence of a large number of synchronized nodes and if they interfere with the completion of synchronization.
Synchronization mode with ignoring all transactions with the current(real) time stamp and disconnection from peers who send incorrect data.

setreload=1
setreconnecting=0


 The "setreconnectpresenttime" option is used after synchronization is complete. Reconnects the wallet to another peer in the absence of a new block within the specified time.
The option "timeupreconnectpresenttime" sets the time in seconds.

Used in many cases, for example, to counter the module "TARPIT".

1) default

setreconnectpresenttime=1
timeupreconnectpresenttime=60*20




Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 20, 2019, 10:00:49 AM
#66

New version available

CACHE-Project, SetControlRealTime added

Version : v_6.1.1.28
Version of git : v_0.7.5.138
Subversion : v_0.7.6.40


Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 17, 2019, 01:30:36 AM
#65

 According to the tests results:
The optimal mode -

setreload=0
setreconnecting=1

Extreme mode -

setreload=1
setreconnecting=0

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 16, 2019, 11:13:54 PM
#64
Quote from: brian_nguyen on May 16, 2019, 05:31:17 PM
Quote from: Deff on May 14, 2019, 11:05:36 AM
 The inclusion of many features was tied to the "debug" setting and was not written about this. In this version, this dependency is removed.
Synchronization of blocks is implemented in three modes -

1)
setreload=0
setreconnecting=0
2)
setreload=0
setreconnecting=1
3)
setreload=1
setreconnecting=0

Coinexchange.io installed the latest version of the wallet and synchronized the blockchain from the zero block to check the balance.

Thank you for your dedication to this project Deff. Without you this coin would have died many moons ago. Cheers!

Thanks for thanks, dear friend!
 Smiley
brian_nguyen
legendary
Activity: 1404
Merit: 1001
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 16, 2019, 05:31:17 PM
#63
Quote from: Deff on May 14, 2019, 11:05:36 AM
 The inclusion of many features was tied to the "debug" setting and was not written about this. In this version, this dependency is removed.
Synchronization of blocks is implemented in three modes -

1)
setreload=0
setreconnecting=0
2)
setreload=0
setreconnecting=1
3)
setreload=1
setreconnecting=0

Coinexchange.io installed the latest version of the wallet and synchronized the blockchain from the zero block to check the balance.

Thank you for your dedication to this project Deff. Without you this coin would have died many moons ago. Cheers!
Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 14, 2019, 11:05:36 AM
#62
  The inclusion of many features was tied to the "debug" setting and was not written about this. In this version, this dependency is removed.
Synchronization of blocks is implemented in three modes -

1)
setreload=0
setreconnecting=0
2)
setreload=0
setreconnecting=1
3)
setreload=1
setreconnecting=0

Coinexchange.io installed the latest version of the wallet and synchronized the blockchain from the zero block to check the balance.
Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 14, 2019, 09:34:44 AM
#61

New version available

CACHE-Project, All features are enabled and available

Version : v_6.1.1.27
Version of git : v_0.7.5.136
Subversion : v_0.7.6.39


Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 06, 2019, 11:54:19 AM
#60
 A second website organized using Shift Project Phantom dApp

http://shiftphantom.cachecoin.net

https://wallet.testnet.shiftnrg.org/ipfs/QmNaN3abndyddukwDSwcRY37MvLzNbXidDqd1nHv9k6HTG/index.html

Deff
sr. member
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
May 01, 2019, 08:33:51 AM
#59

New version available

CACHE-Project, Modifying the block chain request rule in case of transmission failure during synchronization

Version : v_6.1.1.25
Version of git : v_0.7.5.133
Subversion : v_0.7.6.37


four3200
sr. member
Activity: 1246
Merit: 257
Re: 'CACHE'Project [VALM-Cache difficulty recalculation algorithm, SpamHash Control]
April 25, 2019, 11:02:05 AM
#58
can't say no dev here  Grin
cool to see solid activity for CACHE, old project that goes back to cryptsy days.
Pages:
Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)
Jump to: