 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
Still on the sell!!!
Questions do not hesitate to ask!
You have not provided information what cryptocurrencies you accept and what are the possible price ranges for these domains. If you accept payment in Bitcoin, in my opinion you have a better chance of finding a customer when you post this offer in Marketplace> Goods> Digital goods here: https://bitcointalk.org/index.php?board=93.0In addition to what you said, i was surprised checking the op's post history; he almost post only in the altcoin section with some informative posts. By posting here, he seems not to be conscious about how to post for paid offers. I want to try to explain it in simple words; to specify a certain payment method is mandatory to chose in which board you should post about it. So you just have to specify it in main op. About the offer, i think it's a little bit interesting as op seems he had spent enough time building a great profile for some digital goods. I will keep an eye to this thread wishing him the best of luck  You are right, I am here since 1 year almos and with the only interests on some sort of things and one day just thought to buy this domains to sell them And nope, I am not 100% conscious, could you tell me how I am suposed to do: to specify a certain payment method is mandatory to chose in which board you should post about it. So you just have to specify it in main op. Sorry my english is a bit rusted and weak Great! thanks for your interest! |
|
|
|
Still on the sell!!!
Questions do not hesitate to ask!
You have not provided information what cryptocurrencies you accept and what are the possible price ranges for these domains. If you accept payment in Bitcoin, in my opinion you have a better chance of finding a customer when you post this offer in Marketplace> Goods> Digital goods here: https://bitcointalk.org/index.php?board=93.0Done! And yes, I will post in that section too, thanks for your time spent on giving adviece |
|
|
|
|
Bump!
How I am suposed to test the coin before launch it?
Thanks!
|
|
|
|
|
Still on the sell!!!
Questions do not hesitate to ask!
|
|
|
|
OP kindly replace those coins and tokens you choose to Polkadot, avalanche, solana and if you are looking for something more cheaper under 1$ maybe go for GALA, metahero, Alutra, saito and many good altcoins not shiba or doeglon they are shit coins
I will check them, and thanks for all coments, will help me to go futher |
|
|
|
|
Hi there!
Happy New Year!!!
Anyone giving me some adviece?
Thanks!
|
|
|
|
|
Hello there
I still have my teories about bitcoin, crypto, etc. I decided to invest 50€ in some coins with the objetive to hold and if the market makes them rise, I will get that 100x or 1000000x (I am assuming it is day by day more dificult, but not impossible)
Also to learn how works all this up and down, and psicologic facts before I invest real money
Rigt now, holding:
Crypto.com
- Dogelon +3 million coins
- ShibaInu 145K coins
Crypto.com Defi
- TONIC +3 million coins
My strategy is to invest in shitcoins 5-10 euro and hold them, I know isnt the best, but im more concened to invest my money in Value or Indexin for now till I have more knowledge about investing in crypto markets
Could you give me some advieces of this type of coins wich you have consider to get?
Could you give me some coins (not shitcoins) to spend some money to check status and use them for my entry?
Thanks!
|
|
|
|
|
Hi there!
Anyone interested?
We keep it up!
|
|
|
|
1- so I can maintain them as the bitcoin original right? wanted to change to make it "unique" I'm sorry but I fail to understand what you're trying to mean here and because words matter in this subject, I'll have to ask you to repeat it in another way. I was meaning that If I change the letters so was "styling" or making it diferent from bitcoin ones, nevermind it, ill keep them from bitcoin, i guess it doesnt matter 2- sorry didnt understand fine your answer, never tested if the coin works You have to make it work first and then check for these secondary changes.[/quote] Could youplease tell me how I am supposed to test the coin if I did not managed to finish it? I mean, before building it i guess1- Do we work on RPC and P2P ports on chainparams? What do you mean “we work”? Whenever you want to establish a connection you'll use those ports, yeah.[/quote] I was meaning to edit them jejeje (what a failing english related to crypto...sorry for it) |
|
|
|
Well I followed my instinct and done everything Right now, after going for the genesis block, I would like to ask some questions about the development: 1- Do we work on RPC and P2P ports on chainparams? 2- What about the seeds? Do they need to be chainged? 3- In coin distribution (max supply, block rewards, halving interval, block time, sieze, BIPs) are needed to be changed? 4- if the answer of 3 is YES, does it mean that I am making my own way to have own blockchain, meaning it as HARDFORK? 5- Doing my own Genesis block means also HardFork? 6- If bitcoin gets updated to 0.23 and my coin is 0.22, as softfork I can update the changes with the original bitcoin? and as HardFork I coulndt update right? Right now, I want to do my own genesis block (I know that in your tutorial doesnt appears) So, AFAIK I found information about; Old tutorial found: https://medium.com/@jordan.baczuk/how-to-fork-bitcoin-part-2-59b9eddb49a4For me, it keeps understanding that making my own Genesis Block is hardforking Thanks for your time if you answer |
|
|
|
Well, I go further and ask also, on your tutorial, you say: We have to set the difficulty equal with 1, since you will be the only miner at the beginning. At chainparams.cpp change nMinimumChainWork:
Code:
consensus.nMinimumChainWork = uint256S("0x0000000000000000000000000000000000000000000000000000000100010001"); I guess you mean to change every nMinimumChainWork to ("0x0000000000000000000000000000000000000000000000000000000100010001") on all the lines that we can found on the chainparams right? Also, in the next step, when you say to delete vSeeds.emplace_back, you mean to delete complete lines from the chainparams? vSeeds.emplace_back("seed.XXXXcoin.sipa.be."); // Pieter Wuille, only supports x1, x5, x9, and xd
vSeeds.emplace_back("dnsseed.bluematt.me."); // Matt Corallo, only supports x9
vSeeds.emplace_back("dnsseed.XXXXcoin.dashjr.org."); // Luke Dashjr
vSeeds.emplace_back("seed.XXXXcoinstats.com."); // Christian Decker, supports x1 - xf
vSeeds.emplace_back("seed.XXXXcoin.jonasschnelli.ch."); // Jonas Schnelli, only supports x1, x5, x9, and xd
vSeeds.emplace_back("seed.btc.petertodd.org."); // Peter Todd, only supports x1, x5, x9, and xd
vSeeds.emplace_back("seed.XXXXcoin.sprovoost.nl."); // Sjors Provoost
vSeeds.emplace_back("dnsseed.emzy.de."); // Stephan Oeste
vSeeds.emplace_back("seed.XXXXcoin.wiz.biz."); // Jason MauriceThanks for your time! |
|
|
|
About the bech32_hrp code, shouldn´t be changed when you change the adresses? Why do you want so bad to change the prefixes? Have you tested to see if your altcoin is working? The prefix/styling is secondary. Also, in line 244, if I have to change that bech32 code, I have done it right? or should be another letters? It seems fine. I don't cross my arms that you just change that variable and the “bc” prefix becomes invalid. 1- so I can maintain them as the bitcoin original right? wanted to change to make it "unique" I guess the best is to leave it like it was 2- sorry didnt understand fine your answer, never tested if the coin works |
|
|
|
The SCRIPT_ADDRESS stands for the P2SH addresses, those that start with 3. If you notice it, it has “5” in the decimal version: base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,5); And by going to the page I've linked it you can see the decimal prefixes and their leading symbols: Change it to whatever you want. Same goes for SECRET_KEY & PUBKEY_ADDRESS. oH! GREAT! understood! I will leave it like this (question down also): Line 140: base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,45);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,48);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,128);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};
bech32_hrp = "ac"; Line 244 base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,107);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,65);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
bech32_hrp = "tb"; Line 369 base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,107);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,65);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
bech32_hrp = "ta"; Line 466 base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,107);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,65);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
bech32_hrp = "acrt"; About the bech32_hrp code, shouldn´t be changed when you change the adresses? Also, in line 244, if I have to change that bech32 code, I have done it right? or should be another letters? |
|
|
|
and what happens with the scrip_adress? shouldnt be changed? or its only pubkey? Yes, you can change the SCRIPT_ADDRESS too in the same way. but what is the meaning of chainging it? I mean, if pubkey is something that people sees, for what is the script adress, what it is? also, I only need to change the pubkey, not the script right? |
|
|
|
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(120,75); It should be like this: base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,75); Don't change the “1”, just the number next to it. and what happens with the scrip_adress? shouldnt be changed? or its only pubkey? I remember time ago that it needed to be changed |
|
|
|
*It is really fine? as my point of view those 3 parts should have diferent prefixes, or i am wrong? It seems fine to me. You've only changed the signature message and the port number, right? I stuck since I really don´t understand 100% this configuration and what should i do In my tutorial, I've added this as an example: base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,75); The “75” defines that the addresses will start with the letter “X”. You do the exact thing for any prefix. Choose the leading symbol and replace the number with its decimal version. - 1 - Yes, signature and port number - 2 - Ok, I understand that this makes the adress for each "user" / "direction" How about if I leave it like that? If not, I will choose 120 q 34 It should be like this right?: ORIGINAL:
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,0);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,5);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,128);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,111);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,196);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
CHANGED:
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(120,75);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,5);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,128);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(120,75);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,196);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
Sorry if I dont understand clrearly, some technical english is kinda hard for me Thanks in advance! |
|
|
|
Building genesis in linux right? excuse me for asking maybe stupid things, between language and that I am a bit rusted.. You can either build it in linux or windows. May I assume you're a Windows user? Just install gcc and run gcc genesis.c -o genesis.exeI might start all over with your tutorial, since i worked on bitcoin 2.1 and now is 22.00 You mean 0.21, right? Hi black hat! Hope you dont mind I quote you, could you help me to check whats wrong in my move in the last post? thanks a lot, and hope doesnt disturbs you thnx |
|
|
|
First stuck Hello there! Well, I just started and im stucked at this point of your tutorial; Now we will choose a different signature message in pchMessageStart of chainparams.cpp. This is a very important step, if it is not changed and you connect to a bitcoin node it will consider the bitcoin blockchain as the correct one. Do it like this: Code: pchMessageStart[0] = 0xf0; pchMessageStart[1] = 0xb0; pchMessageStart[2] = 0xb0; pchMessageStart[3] = 0xd0; Optional, but you can change the address prefix too. (1, 3, bc1) Link of all prefixes: https://en.bitcoin.it/wiki/List_of_address_prefixesIn the base58Prefixes of chainparams.cpp I will show an example of the "X" prefix: Code: base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,75); First part, I have succesfully* done changing the 3 part where the pch message on the chainparams neded: pchMessageStart[0] = 0xf0;
pchMessageStart[1] = 0xb0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;
nDefaultPort = 17333;
nPruneAfterHeight = 1000;
m_assumed_blockchain_size = 40;
m_assumed_chain_state_size = 2; pchMessageStart[0] = 0xf0;
pchMessageStart[1] = 0xb0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;
nDefaultPort = 17444;
nPruneAfterHeight = args.GetBoolArg("-fastprune", false) ? 100 : 1000;
m_assumed_blockchain_size = 0;
m_assumed_chain_state_size = 0; pchMessageStart[0] = 0xf0;
pchMessageStart[1] = 0xb0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;
nDefaultPort = 17444;
nPruneAfterHeight = args.GetBoolArg("-fastprune", false) ? 100 : 1000;
m_assumed_blockchain_size = 0;
m_assumed_chain_state_size = 0; *It is really fine? as my point of view those 3 parts should have diferent prefixes, or i am wrong? But, when I want to go to the step: base58Prefixes I stuck since I really don´t understand 100% this configuration and what should i do (for me is important to know for what is this and how should I do fine)Las time ive done it i followed this from another source: Change address prefixes Finally, let’s dive into the source code. Currently there are 3 standard address types in Bitcoin: Pay to Pubkey Hash Mainnet prefix “1” Testnet/Regtest prefix “m or n” Pay to Script Hash Mainnet prefix “3” Testnet/Regtest prefix “2” Bech32 (Segwit) Mainnet prefix “bc1” Testnet prefix “tb1” Regtest prefix “bcrt1” Since these addresses are base58check encoded (except for bech32 which is it’s own custom encoding), we can set any prefix we want by using this helpful table of values found at https://en.bitcoin.it/wiki/List_of_address_prefixes. The source file containing these prefix settings is src/chainparams.cpp: // Mainnet: Line 140
// ...
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,0);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,5);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,128);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};
bech32_hrp = "bc";
// ...
// Testnet: Line 244
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,111);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,196);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
bech32_hrp = "tb";
// ...
// Regtest: Line 344
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,111);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,196);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
bech32_hrp = "bcrt";
... We want our p2pkh addresses to start with the letter “K” on mainnet and “k” on testnet and regtest. Then we want p2psh addresses to start with “L” on mainnet and “t” on testnet and regtest. We’ll keep secret keys the same, but we’ll change the bech32 addresses to “lc”, “tl”, and “lcrt” for mainnet, testnet, and regtest respectively. Based on the values in the table linked above, our chainparams.cpp becomes: // Mainnet: Line 140
// ...
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,45); // K
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,48); // L
// ...
bech32_hrp = "lc";
// ...
// Testnet: Line 244
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,107); // k
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,65); // t
// ...
bech32_hrp = "tl";
// ...
// Regtest: Line 344
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,107); // k
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,65); // t
// ...
bech32_hrp = "lcrt";
... |
|
|
|
|
