Bitcoin Forum
November 15, 2019, 03:22:40 PM *
News: 10th anniversary art contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 »
1  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: May 06, 2019, 05:10:25 PM
I created a GMP branch that replaces bignum with GMP. This should eliminate compile errors when using newer versions of libssl. I have tested on Ubuntu 16.04 and 18.04 with libssl 1.1. I was able to sync from scratch and have been running for a couple days with no issues.

I haven't updated the build system. For now you need to compile using ./configure LIBS=-lgmp
Can someone help with this?
2  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: April 22, 2019, 01:20:22 PM
Why in some blocks there is 22,66666666, and not 25 ric?

These are from the superblocks. Once a week there is a superblock with a difficulty about 45% higher than usual. These have a reward of of 694.66666666 and take 70 minutes to find on average. The 287 blocks around that superblock are slightly easier than usual to find and have a reward of 22.66666666.
3  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Riecoin v0.16.3.0 on: January 25, 2019, 09:45:41 PM
Major new version

Binaries and source code:


Thanks for your help with this release.
4  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: January 15, 2019, 07:04:52 PM

Ah, I think I found some of your technical issues... My impression is that I don't think transaction size should be any issue for Riecoin since we will most likely never approach scaling issues like upstream. I wasn't aware of any issue with zero-fee transactions and segwit, if a miner wishes to mine them I don't see a reason why that is not allowed (that would be a pool or miner setting, correct?).

Segwit's benefits for Riecoin are beyond scaling though, Script versioning and MAST, Schnorr, others come to mind.

The issue of zero-fee transactions is independent of segwit. I don't think they are possible, but they can be set to .00000001.

Here is what I wrote a couple months ago.

Quote
I looked into transaction fees a a bit. I think there is enough flexibility through configuration options that we don't need to add a zero transaction fee capability. The parameters are:
mintxfee           - the minimum transaction fee in RIC/kB
minrelaytxfee  - the minimum transaction fee for a node to relay the transaction in RIC/kB
blockmintxfee  - minimum fee for a transaction to be included in blocks created by mining code, in RIC/kB

The defaults are all 0.00001000 RIC/kB. The smallest value is .00000001.

-mintxfee=.00000001 -minrelaytxfee=.00000001 -blockmintxfee=.00000001 will allow transactions of 1 satoshi (or gatra). I have tested this on testnet.

This way we allow users, nodes, and miners to determine what rates should be instead of fixing it in code and we stay consistent with bitcoin.

I could see possibly lowering the defaults.

Two other values that might be useful:
fallbackfee           - the standard fee, defaults to 0.00020000 RIC/kB
m_discard_rate    - any change smaller than this is considered dust and is added to the transaction fee, default is .00010000
5  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: January 12, 2019, 03:36:04 AM
May we have some instructions for how to signal BIP's? I am mining solo and wish to vote.

support for BIPs is indicated through the block version number. If you use rieMiner support should automatically be given.
6  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: January 08, 2019, 03:20:23 AM
I tested CLTV on testnet and it worked fine.

I'll take a look at the pull requests and then move on to CSV.

7  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 26, 2018, 03:48:58 AM


Ok, so I tried compiling Riecoin 16.3 I got a couple errors.  Maybe it is because I am using Boost 1.58 from Trisquel OS?



The test units have not been updated and won't compile. To eliminate the errors you need to re-configure.

./configure --disable-tests
make

This should be fixed shortly, at least so that the test units compile.
8  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 18, 2018, 03:34:36 PM
I've looked at Gapcoin. I even mined some a while back. They were recently delisted by Cryptopia. I could probably create a 0.16.3 version of the code. I'd be far more interested in doing that if others here also contributed. There are some possible issues with the coin that I would like to see addressed before doing any work on gapcoin.
9  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 18, 2018, 03:03:19 PM
Pttn, Thanks for taking the lead on this. I'm happy to be a developer.

Cryptapus, I'll take a look at the gitian code.

There is not much needed to finish the 0.16.3 code. I need to review the gitian changes. We need to set the blocks that BIP65 and BIP66 will become active. We need to decide if we would like the ability to activate segwit or csv. CLTV and CSV should probably be tested. There are a couple things that I added to the code for testing like getwork support that can be removed now.

More developers would be great. Aside from testing CSV and CLTV there probably isn't much to do until after 0.16.3 is released. You could start looking at changes needed in 0.17 code. There will be plenty to do in upgrading the algorithm which is really my biggest interest. We also need web developers.
10  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 09, 2018, 10:01:55 PM
I've merged the pull request and updated the 1000000 block thresholds in the repository.
11  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 06, 2018, 05:05:49 PM
For the Merkle Root, I tried to use sha256^2([nVersion][txins][txouts][nLockTime]) = txid instead of hashing the whole Coinbase Transaction

This is correct. Remove the marker/flag (0x0001) and the witness field (0x0120 plus 32 bytes of 0). Keep the default witness commitment in the txouts.

The scriptPubKey is different for the 'T' transactions (P2SH). (BIP 141)

        0xA914{20-byte-script-hash}87 instead of 0x76A914{20-byte-hash}88


It's different still for 'bcr' addresses (P2WPKH or P2WSH).

        0x0014{20-byte-hash} or 0x0020{32-byte-hash} depending on length.
12  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 05, 2018, 06:59:23 PM
One possibility, it looks like you are creating a standard transaction for the coinbase instead of a witness transaction (see BIP141). For a witness transaction you need to add marker (0x00), flag (0x01), and a witness. For coinbase, the witness is the "witness reserved value". I'm not sure what witness reserved value is used in calculating the default_witness_commitment.

EDIT: It looks like the "witness reserved value" is 32 bytes of 0x00.
13  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 05, 2018, 03:58:29 PM
Thank you clo1 for these useful links. I updated rieMiner to include SegWit support (at least experimental for now) after struggling to understand how and where I had to put that default_witness_commitment.

rieMiner is now able (if the segwit Rule is set in the options, like below) to mine Segwit transactions between "t" addresses in TestNet, and also blocks with mixed segwit + legacy transactions, so I assume that rieMiner is now SegWit ready in case it ever gets actived. It also worked with legacy transactions produced by 0.10.2 in Testnet too, so current normal mining should be unaffected. More testing is welcome, and I invite you to comment the update if needed clo1, you are the expert.

I added a "Rules" option where one can add rules for the GetBlockTemplate call. For example,

Would this be enough for indicating support for the remaining softforks and use them? What rule strings do we have put for Bip 65, 66, etc if we want to indicate support and use if they are activated? I just know that for SegWit, it is "segwit"... Would I need to do something else to support properly these softforks?

It's great that you got these working. I'm hardly an expert in these softforks. There is nothing to do for BIP65, BIP66. Once the activation block is reached the rules are automatically enforced all the time.

The only untested parts of the code now are CSV and CLTV. These allow creating transactions that can't be spent until some time in the future. I haven't touched this code so they should work. I don't think there is an easy way to create these transactions. I think they require creating custom scripts using python or node.js or maybe riecoin-tx.
14  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 04, 2018, 06:20:58 AM

Could you give me some documentation about these? I need to know precisely everything I have to do to implement these features in rieMiner. I plan to release the first stable rieMiner 0.9 version in December 16, it would be great that until then, it provides everything needed for 0.16.3.

Else, you can do these yourself and make pull requests as you seem to be very knowledgable about Bitcoin Core code (honestly, I am not that good in this field). For anything involving the Coinbase, everything is in GetBlockTemplateData::coinBaseGen() in GBTClient.cpp for GetBlockTemplate. For Stratum, as the Coinbase comes from the pool, owners will need to upgrade their code as well.

"In the transactions you need to use the txid field instead of the hash field." What do you mean?

I have heard about support bits for Softforks, do I need to implement them, or they are already included in the GetBlockTemplate call? I think that we could add these support choices as options in the configuration file if needed.

Also, could you please merge my pull request that updates remaining Bitcoin icons to Riecoin ones?


I couldn't find documentation showing exactly what is needed anywhere but here is some:
soft forks
https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki#getblocktemplate_changes

segwit
https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki
https://github.com/bitcoin/bips/blob/master/bip-0144.mediawiki
https://github.com/bitcoin/bips/blob/master/bip-0145.mediawiki

some pages I came across while searching for default_witness_commitment
https://bitcointalk.org/index.php?topic=1674590.0


Some observations:
To activate segwit you first have to change the activation time window in chainparams.cpp. Change line 213, testnet segwit nTimeout to something really big. If we decide to activate segwit we will change the mainnet timeout to something reasonable.
        consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nTimeout = 14935968000 // I added a 0

Once this is done 'segwit' will show up in the vbavailable field of getblocktemplate. The correct bits were already set in version so there is nothing to do here.

You then need to mine 2 full cycles of 288 blocks before segwit activates. I've already done this on testnet.

Once activated getblocktemplate will return 'segwit' in the 'rules' field. Segwit transactions can now be added to mempool. In order for them to show up in the getblocktemplate call you need to add a parameter to the call.
   jsonGbt = sendRPCCall(_curl, "{\"method\": \"getblocktemplate\", \"params\": [{\"rules\":[\"segwit\"]}], \"id\": 0}\n");

From BIP145, 'when witness transactions are included in the block, the primary merkle root MUST be calculated with those transactions' "txid" field instead of "hash" '.
        hexStrToBin(json_string_value(json_object_get(json_array_get(jsonTxs, i), "txid")), txHashInvTmp)

Also from BIP145,  'a secondary merkle root MUST be calculated as per BIP 141's commitment structure specification to be inserted into the generation (coinbase) transaction'. I believe this is in the default_witness_commitment field of getblocktemplate. I stopped here for now. I didn't want to spend any more time on something we might not activate anyway.

Sorry, I didn't realize there was a pull request. I'll take a look later.
15  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: December 03, 2018, 05:05:48 AM
I took a quick look at segwit on testnet. I was mostly interested in checking the activation process. Pttn's getblocktemplate code handled setting the proper bits without any changes needed so I was able to activate on testnet. After activation, the 'T' transactions were added to the mempool. Some changes are needed in rieMiner to handle segwit transactions.

The miner needs to indicate support for segwit by adding a parameter in the getblocktemplate call in order for the transactions to be sent. I think this will also be needed for csv.
{\"rules\":[\"segwit\"]}

In the transactions you need to use the txid field instead of the hash field.

There is a default_witness_commitment field that needs to be added to the coinbase transaction. I wasn't exactly sure where this goes or the best way to add this to Pttn's code so I stopped here. If anyone else wants to look at it I can help you get to this point.
16  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: November 30, 2018, 10:32:53 PM
With gatra becoming a ghost and no trace from past developers, this project is becoming chaotic and stagnating. In order to advance, we need to be well organized, and to find and choose active and consistent people supporting the project.

So, I propose that we compose a new Riecoin team. Here is a suggestion of some important roles to assume:

  • Leader(s): this role will simply replace gatra. Someone taking this responsibility will ensure that Riecoin goes in a good direction, that all other team member are doing well, and will take important decisions, like making Riecoin Core official or deciding if a fork should happen. These persons will represent Riecoin and for example be in charge of contacting exchanges for listing Riecoin. Also, they decide who are part of the team;
  • Developers: we need people for maintaining Riecoin Core, rieMiner and any other important Riecoin software. There should be more than one developer working on Riecoin Core, and they should be able to catch up important Bitcoin Core updates quickly. Everyone here has to ensure that the code never becomes outdated. Motivated pool owners are also welcome to be part of the team;
  • Community Manager(s): for advertising Riecoin and spread its use. Someone assuming this role should be continuously searching for new communities to reach and be active in the Riecoin related forums (answer to questions, reply to people asking why Riecoin is a good altcoin,...).

We also need a new official website, and at least one person of the Community Managers has to maintain it. The website would contain explanations, links to important websites (community, exchanges,...) and softwares, official downloads, a news section, etc. We have riecoin-community.com, though I am not sure if IGJ is willing to create and maintain a new official website.

Also discuss/debate about this idea in this topic. I hope that there will be motivated people willing to be a lot active for Riecoin.

Also, I remind this clo1 post:

The softforks haven't been tested yet but I don't expect any problems here. The older BIPS are coded to become active at a specific block. I have currently set them to become active at block 1000000 but this can be changed to a block that will be reached shortly after the code is released. Once this block is reached any block mined with an old miner (using an old block version number) will be rejected even if the block is otherwise perfectly valid.

The newer BIPS become active if a super-majority of blocks are mined using a miner indicating support. I believe it is 95% within a 288 block window. This must occur within a specific time window which we will need to set before releasing code.

For people currently using 0.16.3, we need to agree about these softforks or change the 1000000 value for a later decision. There is less than 5000 blocks remaining!

Thanks for posting this. I agree and was going to post something similar. In the short term, I think a new official website and releasing official 0.16.3 code are most important.

For those who want to continue running 0.16.3 after block 1000000, lines 85 and 86 in chainparams.cpp need to be changed. Just make it something really big like 2000000 for now. I thought 1000000 would be enough when I first wrote it. I can update this in the riecointeam repository as well.

I did a quick check of BIP66 on testnet and it worked fine. Is anyone familiar with CLTV (BIP65) or CSV (BIP68, 112, 113)? Can you help me create a couple tests to show that these are working? I think BIP65 was one of the requirements for Barter Dex. We still need to decide if we want to activate segwit.

Also, I submitted riecoin's largest primes to the record list. Riecoin currently has spots 3-11 on the biggest 6-tuples.
17  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: November 01, 2018, 03:27:38 AM
I looked a little more at the problem of not being able to spend from 'T' addresses (P2SH). The default address type is P2SH-segwit, a segwit address wrapped in P2SH. Since segwit hasn't been enabled the transaction is rejected. It would probably work once segwit is enabled but I haven't tested this. The other address types are legacy and bech32 (segwit). Legacy P2SH addresses can still be created for instance using addmultisigaddress with address type set to legacy. I tested this on testnet and was able to send coins to the address and spend them.

If we aren't going to enable segwit we can set the default to legacy. We could also make it so that other types cannot be selected. Let me know, it will be one less thing to test.

I'm not aware of any other issues. The soft forks should probably be tested. I'll try to start this week.


18  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: October 30, 2018, 02:27:58 AM
For beginners here, I wrote a Getting Started page in my Riecoin website.

Additionally, I created a Profitability Calculator.
To use it, you need to get the 2 to 4 tuples/s metrics by benchmarking using rieMiner during enough time.
Do not hesitate to report if you find something flawed in the calculator.

Difficulty scaling should probably be 9th power instead of 6th. The prime checks are proportional to difficulty ^3 so it is constellation length + 3. This is what riecoin uses in computing difficulties.

The primecheck uses multiplications. For multiplication it should be the number of words rather than the number of bits that matters. It's possible you would get more accurate results with:
(d2/d1)^7*ceil(d2/64)^2/ceil(d1/64)^2
I'm only suggesting this for the calculator, not for riecoin.
19  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: October 13, 2018, 10:05:57 PM
I looked into transaction fees a a bit. I think there is enough flexibility through configuration options that we don't need to add a zero transaction fee capability. The parameters are:
mintxfee           - the minimum transaction fee in RIC/kB
minrelaytxfee  - the minimum transaction fee for a node to relay the transaction in RIC/kB
blockmintxfee  - minimum fee for a transaction to be included in blocks created by mining code, in RIC/kB

The defaults are all 0.00001000 RIC/kB. The smallest value is .00000001.

-mintxfee=.00000001 -minrelaytxfee=.00000001 -blockmintxfee=.00000001 will allow transactions of 1 satoshi (or gatra). I have tested this on testnet.

This way we allow users, nodes, and miners to determine what rates should be instead of fixing it in code and we stay consistent with bitcoin.

I could see possibly lowering the defaults.

Two other values that might be useful:
fallbackfee           - the standard fee, defaults to 0.00020000 RIC/kB
m_discard_rate    - any change smaller than this is considered dust and is added to the transaction fee, default is .00010000
20  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record on: October 12, 2018, 06:45:05 PM
As IGJ mentioned, transaction version 2 indicates support for BIP68. This allows transactions which aren't executed until some time in the future. I don't think there is a problem with temporarily changing this to 1.

I mentioned earlier that transactions that start with 'T' could not be spent and recommended only using legacy addresses. I think the problem is that a witness is being attached, but segwit has not been activated yet so it is rejected. I'll look into why the witness is being attached. You may be able to get around this with prematurewitness=1. I haven't tested this and I'm not sure what 0.10.2 would do with the transaction.

I will also look into allowing transactions with no fee, but not sure if this is good or bad.

I also have no preference regarding segwit. As the code is now, it will never be activated. We would need to change the start and timeout times for it to be capable of being activated.

Yes, I used Pttn's suggestions for prefixes. He won with a vote of 1-0. I think there is one other 'T' transaction about a month ago.

It is good that people are starting to use the new version. Just be aware that BIP65 and BIP66 are set to become active at block 1000000 which should be early December. When this happens, all blocks mined with current miners (other than the current rieMiner attached to a 0.16.3 node) will be rejected by the 0.16.3 code. The block version, which is is different from transaction version, will need to be at least 4 to be accepted. If 0.16.3 doesn't become the official code by then, those who are running 0.16.3 will need to increase the 1000000 to something larger.
Pages: [1] 2 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!