Topic: [ANN][GAP] Gapcoin - Prime Gap Search - New Math Algo - CPU / GPU - Zero Premine - page 3. (Read 286844 times)

Some good blocks, above 30 (only those valid as a current improved record):
cf. Submissions


Merit 31.21 - 06-05-2021


Merit 31.76 - 04-05-2021


Merit 31.99 - 01-06-2021



60M PPS yesterday :

Update to 0.16.3 client, “extended” version

Seth Troisi, of the Mersenne Forum's Prime Gap Search group, has slightly changed the way that the prime gap list is maintained and the URL for the latest list (allgaps.sql) has changed, necessitating an update of the Gapcoin 0.16.3 extended client (the "minimal" version doesn't have the checkprimegaplist RPC API facility so is unaffected).

If you're using a downloaded binary of the 0.16.3 extended client version and want to use the checkprimegaplist console/RPC-API call to monitor the as-yet-uncommitted Gapcoin records, you need to download a fresh binary from the Github releases. (If you're running a self-compiled version, just git pull and recompile.)

Cheers

Graham

Gpu commands are:


YOu can download fermat.cl from here https://github.com/wizz13150/GapcoinStuff/blob/main/Custom/fermat.cl and compare with orginal fermat.cl

Hey Benxy031, can you either post here the Fermat.cl file changes here or open a Pull Request here https://gitlab.com/gapcoin/gapminer

The GapMiner Compiles now using MX-Linux.

I have never used the GPU miner so if you can list the Command Line Commands too I can include it into the Readme file otherwise after I try the GPU miner I will list them myself. 

I am mostly interested in double checking your Fermat.cl changes before I merge it......

Upgrade of Gapcoin Core client from 0.9 to 0.16 completed.

I fixed the issue that caused the client to create excessive demand on the RPC work queue and I have now completed the process of upgrading the Gapcoin client from 0.9 to 0.16.

There are two releases, one for a “minimalist” version and one for an “extended” version (with extended GUI and RPC-API functionality):

https://github.com/gapcoin-project/gapcoin-core/releases

Cross-compiled binaries are available, along with the scripts (one for each version) used to generate the binaries (Ubuntu-0.18 VM/host recommended) and a zipped bootstrap.dat file (be prepared to wait a day-and-a-half to a couple of days to sync from 0 if using -loadblock=bootstrap.dat).

Due to changes in the structure of the wallet code, the 0.16.3 client cannot load a wallet.dat saved by an 0.9 client. You can't simply copy the wallet file over, you have to use the dumpwallet command in the command-line/console in the 0.9 client to create a text dump of the wallet. Then, in the 0.16.3 client, use the importwallet command in the command-line/console to import the dumped wallet.

Step-by-step procedure:
0.9 client

0.16.3 client

(and wait for a few hours while the client scans the entire blockchain's tx history, rebuilding your UTXO set).

Yes.

This is my personal development area, following the convention for contributions: “The codebase is maintained using the "contributor workflow" where everyone without exception contributes patch proposals using "pull requests".”

Kinda. Just the same as everyone else operating in a decentralized space, I’m obliged to take my cue from the community and its collective response to technical contributions.

As far as the 0.9 client is concerned, I won’t be spending any further time/effort in that direction, either in terms of development or support.

The presence of 0.9 clients in the Gapcoin network does act to constrain some of the functionality of the 0.16.3 client. A couple of examples:

1. Users will note that in the provided example.gapcoin.conf, the configuration peerbloomfilters is set to 0, effectively disabling the bloom filter optimisation used in network connections. The reason that this service has been disabled in the config for the 0.16 clients is that 0.9 clients are unable to handle bloom filiter messages and register an error in the log.

2. There is no means of preventing 0.16 clients from creating transactions using segwit addresses which, although not actually causing an error in the 0.9 client, causes it to treat such transactions as “nonstandard” and basically, misrepresent them.

Here's an example from testnet, txid 94cfec5d7da0853f2ba04a3a23957171027a2875a5f43b8cc9bf3cf19d4a5aff

As reported by the 0.16 client:

As reported by the 0.9 client:


At some future time, when a significant majority portion of the Gapcoin network is hosted by 0.16 clients, we can increment the version number and set appropriate values in chainparams.ccp to enable the community to signal its acceptance of a phased transition to a full segwit-enabled network. At that point we can discuss the issue of incrementing the minimum version number in order to exclude relatively-incapable 0.9 clients from the network.

The 0.16.3 client is the only one that I'm prepared to provide any support for in terms of responding to reported issues and/or providing limited help.

Cheers

Graham

Good news, apparently this Repository will build MX-Linux and possibly most others as well.  

https://gitlab.com/gapcoin/gapcoin

It seems to have been when I tried MX-Linux before I had not started ./configure during the Source Code Compliling using --without-miniupnpc

It compiles and runs good on MX-Linux.  I will work on bringing over Jonn9's Prime-Gap Miner which he programmed to submit the largest merit PrimeGaps into Blocks......

MX-Linux installs Nvidia Graphics drivers easier than Windows, so it will work with https://bitcointalksearch.org/topic/m.56895333


Thanks Benxy031, but I have not Tested this yet for Nvidia GPU Mining

Gapcoin is listed on Coingecko so that's good. No need for coinnarketcap.


https://www.coingecko.com/en/exchanges/freiexchange

OK, I understand.  I like your work on this coin.

The community is overwhelmingly comprised of pseudonymous individuals but CMC won’t respond without an email address - I can't resolve that contradiction without giving them my email address, which I'm not prepared to do.

Cheers

Graham

It's not easy to deal with companies like Coinmarketcap. I did not like them much and when Binance bought them I have more things against them.

There is one more projekt that have taken GAP and maybe there will be a good one that overtakes the GAP.
They should not list other projekts with the same 3 letters. That maybe is easier for them to take care of. They have a placeholder for us so maybe they will be a little easier on us when they see that there is activity here. GAP is not premined so that is a very good thing.
'It's a advertising platform to get more computers to this network and protect GAP as I see it.

I agree that they are not good.

Need to assess whether it's worth the effort.

Stumbling blocks in terms of assumptions of centralized organisation that are inappropriate to a decentralized cryptocurrency:



Cheers

Graham

There are another coin on Coinmarketcap that are listed as GAP.    GAPS/GAP

https://coinmarketcap.com/currencies/gaps/





This coin
https://coinmarketcap.com/currencies/gapcoin/markets/

https://coinmarketcap.com/exchanges/freiexchange/
GAP is further down under unverified markets. 

Need to fill in a rquest form.

Just completed a post on an informal history of the prime gap list:  https://gapcoin-project.github.io/gapcoin/2021/05/06/history-of-the-prime-gap-list/

Cheers

Graham

Dunno. Not completely happy with the getwork implementation. Turns out that the demands of the standalone GapMiner cause the client to run out of rpcworkqueue capacity, doubling it to 64 seems to work but I don't know whether that's practical for pool mining.

In the old client, the mining key is bound on RPC startup but in the new client, its ability to run without a wallet at all made a nonsense of that RPC startup assignment and it's long been removed. So in the 0.16.3 Gapcoin client, the getwork code has to get a miningkey each time it's called, which isn't satisfactory so I want to find somewhere earlier in the process to shoehorn in the binding of the mining key if I can. The other solution would be to rewrite the GapMiner code to use the contemporary (and supported) getblocktemplate RPC call instead of the obsolete (and removed from the upstream cloneparent) getwork RPC call. I have re-implemented the getwork call but it's not a particularly good fit for the way that the 0.16.3 codebase is designed and the extra demand on rpcworkqueue is a consequence of that.

For the last couple of days, I've been confirming that a dumpbootstrap RPC call that I've added actually creates a bootstrap.dat that the client can sync from (it does, albeit the client takes a day and a night to sync from a bootstrap).

Cheers,

Graham

- http://gapcoincore.org is now on forward to https://gapcoin-project.github.io/

Still seeking clarification on ...



... then the new Gapcoin Club and Network nodes will go live in the coming weeks!

FWIW: Are we approaching a re-announcement ?

No-one who cares to check the results.

The list is profoundly out of date and incorrectly credits Gapcoin with the following records, since surpassed by others:


5144, 5158, 5164, 5254, 5278, 5284, 5314, 5334, 5342, 5370, 5380, 5404, 5410,
5420, 5428, 5486, 5502, 5512, 5532, 5556, 5570, 5584, 5616, 5648, 5658, 5682,
5706, 5762, 5808, 5814, 5826, 5880, 5934, 5944, 5990, 6008, 6018, 6028, 6044,
6050, 6076, 6098, 6134, 6144, 6160, 6178, 6190, 6196, 6224, 6226, 6240, 6264,
6278, 6280, 6286, 6310, 6312, 6326, 6330, 6342, 6346, 6348, 6370, 6372, 6378,
6392, 6398, 6400, 6408, 6416, 6418, 6424, 6426, 6428, 6438, 6440, 6450, 6458,
6468, 6472, 6474, 6502, 6510, 6522, 6538, 6552, 6560, 6564, 6582, 6600, 6604,
6608, 6640, 6658, 6666, 6674, 6690, 6712, 6756, 6804, 6856, 6878, 6904, 6908,
6934, 6940, 7006, 7104, 7124, 7158, 7194, 7200, 7276, 7372, 7380, 7390, 7406,
7486, 7538, 7566, 7640, 7648, 7884, 7894, 7918, 7928, 7940, 8066, 8366, 9694,
9860, 10048, 10124, 10696, 13126, 13172, 13196, 13244, 13372, 13376, 13416,
13578, 13612, 13630, 13684, 13686, 13724, 13772, 13918, 13922, 14114, 14124,
14192, 14280, 14294, 14344, 14354, 14454, 14478, 14492, 14498, 14540, 14546,
14602, 14626, 14664, 14672, 14710, 14766, 14802, 14904, 14934, 14976, 15046,
15092, 15124, 15246, 15252, 15270, 15290, 15308, 15374, 15618, 15700, 15852,
20498, 20586, 20742, 21032, 21166, 21202, 21252, 21586, 21654, 21800, 21898,
21990, 22022, 22050, 22140, 22206, 22260, 22848, 22856, 22878, 23042, 23490,
23526, 23824, 24462, 25410, 25470


To ascertain the current status for yourself, import the current prime gaps list SQL insert file into SQLiteBrowser with “File->Import->Database from SQL file”



and in the “Execute SQL” tab (shown above), enter the following SQL query:

SELECT * FROM gaps WHERE discoverer == 'Gapcoin' ORDER BY gapsize;

and then, to see this year's changes:

SELECT * FROM gaps WHERE discoverer == 'Gapcoin' AND year > 2020 ORDER BY merit DESC;

Cheers

Graham

This one is from 2019. The list is probably just growing since trnicely.net is no longer maintained. (Last updated 0600 GMT 12 August 2019)
See: New Submissions, to the new list.

Thank you. And BitcoinFX, indeed.


So the script was started / executed on gapcoin.org... And j0nn9 still doesn't resurface (To say Hello !?)...  
Who did this !? ..Probably no one.

Mod note: Consecutive posts merged

---

New Gapcoin record


length:        16280

shift:           479

old merit:        26.958752

old start:                1837160733118439423867182346994891162127548709911684382984517002398483960870036 6949710878116871579060625070628107877901041700271202527634022039178084473576298 4726077306347442594307484942323549457652749090645002709235558292986289921920320 45727424911933714770667667

new merit:        31.968393

new start:       1464770814484880302194679937357994935470205415296523009666134039594591058062188 0709086367706958449459408280449740553052536108763199187166565199656594412400209 2297149454294244855324271896290939574797498511512977910260881557

record type:       


This Record is a good example of randomness in the blockchain!  (This Shift was lightly mined for a couple days only using 32 Core Threadripper, but the generated waves from surrounding shifts made it score a direct battleship hit) Generating Random using Backdoored Encryption is nearly impossible except to play the real world drama outside!

I propose a future Hard-Fork Gapcoin Blockchain using a Dash Coin Gapcoin Clone but using the X16 Algo all different Gapcoin Mining Shifts 16 different combinations using 16 RANDOM Rounds of encryption layers

And Congratulations the one/ones mining the 800-1100 shifts.......A huge improvement from last year!  I think BitcoinFX is the One/of the Ones

I read on mersenneforum that some off the members there dislikes crypto very much. It did not matter to them that they did not understand the concept. That means that we can't expect them to respect the boundaries of this coin. They are not happy over how ETH have made a shortage of graphic cards and they fear that a new token also will make a shortage of hard drives. So we could also exppect a targeting of this area.

THE good news is that it takes time to find all records in this area and their metod finds records faster but not all off them.

There have been a lack of upgrades of the miners and if we can make them better so we find more records maybe they don't find it so interesting to target this range anymore. There are still a lot of records to be found.