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

True.
I'm on testnet since 07/11/2020, day of pre-release of Alpha available.
C'mon, "pre-release" and "Alpha", seem's crystal clear to me.
Absolutely no indication was given to switch to the mainnet. It's the opposite.
I'll wait.

I also see that a lot of work is done in the shadows. After 6 or 7 years, no need to rush this part there.
So I'll just add Good luck and Good work guys !

Here's an example of a miner that would appear to be mining blocks to a single address ... not me! ... 

- https://chainz.cryptoid.info/gap/address.dws?GUNtDqH8QxesjU9p3TsE7LPkRjtGUykWrp.htm

As mentioned, it's not really a great idea in terms of anonymity or privacy, but I guess it adds some convenience to the mining process.

...

"We Got The Gun by Clint Mansell from Darren Aronofsky's Original Soundtrack"
- https://youtu.be/AFn-Wr3qDTY *Explicit Lyrics*

I debated with myself whether to mention generatetoaddress in my response. Although I haven't checked, because I haven't interfered with any of that particular code, I have no reason to doubt its flawless functioning. The trouble is that in-wallet mining of BTC on mainnet was (correctly) considered futile by the Bitcoin devs as far back as 0.13, nearly five years ago - at which point the code for the internal miner was removed from Bitcoin.

One of the key implications of this is that the remaining generator code in the Bitcoin codebase is intended solely for use with testnet/regtest.

The practical consequences are that generatetoaddress isn't suitable for use as a general-purpose, run-until-stopped miner. The call takes three arguments: the target number of blocks to generate, the address to which they should be credited and, importantly, the maximum number of tries to attempt before returning - generatetoaddress nblocks "address" ( maxtries ) - and then it stops and you need to call it again. It's not that it can't be driven from a bash/Powershell script, it's just that this additional technical demand imposes a higher barrier to entry.

However, the Bitcoin code that implements the address-handling for the generatetoaddress function is obviously a candidate for copying and pasting. If it's perceived as highly-desirable to integrate this functionality into the in-wallet miner, one approach would be to store a mining address in the gapcoin.conf file and pick up the value from that.

Be advised though, having all the mined blocks going to one address compromises anonymity but if there's a compelling use case, I would be prepared to consider putting in the time and effort to get it to work.

Cheers

Graham

Whilst I fully appreciate the predicament, we should all await Stable Release of Gapcoin Core v0.16.3 - across all platforms (hopefully) ...

See: Software release life cycle - Release Candidate (RC)
- https://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate

I personally need some more time to test and review everything.

Gapcoin Core v0.16.3 ...

cd gapcoin-core/src && ./gapcoin-cli help

Excerpt;

See:
- https://developer.bitcoin.org/reference/rpc/generatetoaddress.html

As I understand it, that's the way it's always been with the built-in miner, each block reward is credited to a newly-generated address (these days, actually a scriphash). Rewards credited to specifically-set addresses are feature of pool mining or solo mining with an external miner.

Cheers

Graham

I think the 16.3 Wallet is good for trying to adopt.  I think you should promote it now BitcoinFX.  It's solid mining ect........


The importing addresses will only be harder for new people if they start using the old wallets when they should be using the New one and never have to worry about the import issues.

I wish there was a better way for the wallet import. 

But I think it's best to get it out of the way and deal with the issues as they come up.  Promoting the old wallets will just be negative to the overall goal of getting new people to use Gapcoin. 

Thanks Graham!  

what settings i need for all blocks found on solo mining go to one address for see my adress here https://chainz.cryptoid.info/gap/#!extraction

on this moment all block find go to random generate adress

I was not really aware that I had 'announced' anything as such, rather I posed some questions to the community with a possible upgrade schedule.

However, when an alpha Release Candidate is available for download, people often take it as read that they can safely 'upgrade', which is clearly not the case.

I did not add the windows alpha Release Candidate to https://gapcoin.club

The new core repository is made available as a link, in the hopes of attracting additional developers to assist Graham ...

"Linux Build - Gapcoin Core v0.16.3 - Work in progress - v0.16.3-rc-alpha"


Also see: https://bitcointalksearch.org/topic/m.56186392

We have a Gapcoin testnet.

- https://bitcointalksearch.org/topic/m.55546099

Please don't rush to 'upgrade' on mainnet, before any 'official' release announcements are made.

Graham is continuing to do sterling work in regards to development and I hope others will become more involved with helping as we progress.

Mod note: consecutive posts merged

---

You have a choice of hand-importing to the 0.16 client each of your 0.9-dumped privkeys or using the 0.9-dumpwallet/0.16-importwallet process to do it in one step. I can't see why it'd be any easier with a backed-up wallet but in any case, always back up the wallet before any significant admin, it's just good practice.

Thanks for the kind words, btw.

Cheers

Graham


Now fixed.

BitcoinFX's announcement caught me unawares somewhat as I hadn't taken the opportunity to go through the code in detail to ensure as best I could that all the work-in-progress was properly tidied up. In the event, I overlooked a stray line of developer-convenience code that, under a set of conditions that I apparently couldn't actually replicatet (although I glimpsed the fault briefly on one occasion) had the effect of inappropriately activating the inscription field placeholder text as though the user has pasted it in. I've removed the developer convenience but that was only part of the problem - the inscription/notarisation facility uses OP_RETURN data and any such transactions should only ever be send-to-self, which wasn't being enforced --- but it is now. I took some time to rework that section completely and now OP_RETURN transactions MUST have an amount of 0, that should prevent any more coins going astray via that route.

I've sent M0ndialu 500 GAP, to reimburse his loss and as a token bug bounty.

To avoid the possibility of losing coins, please refrain from making transactions with the 0.16.3 client until you've switched to the new binaries/source code pre-released as 0.1rc-beta: https://github.com/gjhiggins/gapcoin-core/releases/tag/v0.1rc-beta

Sorry for the convenience.

Cheers

Graham

Thanks Higgins........it's too bad about Old Wallet not working with 16.3.   Is it easiest to transfer Coins into a new Wallet that is backed up? 

In 16.3 in-wallet mining seems to be working, no errors using 20 GB Memory.

Have not mined a block yet, but optimistic nothing will crash as it seems stable.  The previous error was quick to show up! 

Right. You should now wait until I fix it.

Cheers

Graham

not all time sent work bad, sometimes it worked good  

Good: https://chainz.cryptoid.info/gap/tx.dws?65e82dc94e412535b26c54435f7faf99d0b5b130c41d97afc8d27710e299b47d.htm

Bad: https://chainz.cryptoid.info/gap/tx.dws?507de7422cdec6c912fc64cffbcbf3a1991febca3dd246bcc5db33f84d9517d1.htm

Mod note: consecutive posts merged

---

That's not good. I'll investigate. The client may have inappropriately included what should be placeholder text. If so, I'll reimburse your Gapcoin.

Cheers

Graham

Your apparent disinclination to provide details isn't helpful.

I can't immediately replicate the issue you encountered, there was no issue with the standard 1 GAP tx I sent to freiexchange https://chainz.cryptoid.info/gap/tx.dws?979fbb27e9a31d00e0ba4e395e65037db1b865d0bc61cf00806734584774670e.htm.

Ordinarily, I would enquire whether the common precaution of you sending an initial test low-value deposit of 0.5 GAP was successful but I doubt you did that.

Given that a standard transaction succeeded, it would appear that the Inscription/Notarisation UI isn't as idiot-proof as I hoped, so I will have to suppress that particular feature. I'll make new binaries available in a few hours.

PM me a Gapcoin address and I'll reimburse your 297 GAP.

Cheers

Graham

i try to send 297 gap from new wallet to exchange and give me this

https://chainz.cryptoid.info/gap/tx.dws?c5deecc8a5a606408f00549058c48cf9720827bdfa576f56a6290552d959b785.htm

Not yet redeemed   OP_RETURN.. 

Wizz_^ has been busy with Powershell, creating plots of Gapminer performance. I'm following along at my own pace using Python to configure systematically the miner parameters, start/stop the miner and record the results.

I wrote up some interim notes on my understanding of what changing the settings of the shift parameter means in terms of prime digit length and Gapminer performance and have published them as a standalone HTML page on Mega: https://mega.nz/file/6VUAXLhC#JWC-5OxsZonQ1q0oHlDbqQ2OtAHjWcwbUHUhUgxQ0QM (download and open in browser) got it badly wrong. Will repost in due course.

Cheers

Graham

https://github.com/bitcoin/bitcoin/blob/master/src/crypto/hmac_sha512.cpp

Found the HMAC, looks like it's just as easy to upgrade the key size to 512 Bit Keys. 

This will make me happy enough to have everyone move up to 16.3.

But a new Windows build might need to be done. 



The HMAC is the most important part of Bitcoin, as it's key size is what matters most.  With a distributed Blockchain across the World.

Mining / DataMining Noob Stuff

https://github.com/wizz13150/GapcoinStuff






I got this one, dumb (me) translation :
Allow a range, a network delimited by subnet mask.
Not a single IP nor IP and mask

no work indeed, that's because you didn't follow the instructions. I guess I wasn't clear enough, I intended that you should copy and paste the solution. You did the equivalent of 192.168.1.199.* which is wrong.

I was explicit and precise:

It needs to be valid CIDR (see https://www.ionos.com/digitalguide/server/know-how/cidr-classless-inter-domain-routing/).

Just in case, I'll repeat: you need to use: rpcallowip=192.168.1.0/24 at least, maybe even rpcallowip=192.168.1.0/32 (see above link and do the arithmetic for yourself, this isn't a Gapcoin config issue, this is just a general CIDR networking config issue).


Cheers

Graham

on my old config i have :

rpcallowip=192.168.1.199

and all work good

and on new config i put

rpcallowip=192.168.1.199/24

but no work