Git Product home page Git Product logo

incentivized-testnet-stakepool-registry's Introduction

Incentivized Testnet Stake Pool Meta Data Registry

Background

This repository provides a means to register public stake pool meta data for the Incentivized Testnet. Successful registrations will result in the listing of a stake pool as a delegation option in all of the supported testnet wallets (Daedalus & Yoroi).

Adding your stake pool to this registry is only one of several steps required to get your stake pool up and running. Please refer to the testnet site for a description of the entire process.

Use of this registry is subject to the following usage policy

Process

New stake pool registration

Stake pool registrants will provide signed submissions in the form of Github pull requests into this testnet pool registry. Here they will be subject to automated checking for well-formedness and human vetting before being merged to master.

Stake pool de-registration

This action does not require any changes to the registry -- the inactive pools are simply ignored.

Updating existing entries

Stake pool registrants will provide signed submissions in the form of Github pull requests into this testnet pool registry. Here they will be subject to automated checking for well-formedness and human vetting before being merged to master.

Semantic content of registry entries

Each entry contains the following information:

name necessity description
owner required subject identifier public key
name required stake pool name
description optional stake pool description
ticker required stake pool ticker
homepage required URL of the stake pool's web page
pledge_address required a pledge address
- required signature (verifiable by the public key)

⚠️ The owner public key mentioned here must match your owner public key used for registering your stake pool on chain!

Precise entry validity rules are described in the following section.

Submission well-formedness rules

  1. Submissions shall consist of a single commit, directly off the master branch of the incentivized-testnet-stakepool-registry repository.

  2. Submissions are identified by the subject's Bech32-encoded Ed25519 public key (all lowercase).

  3. Submissions shall either add a new entry or modify one.

  4. Submissions shall involve (addition or modification) of exactly two files, under the registry subdirectory of the repository:

    • the JSON submission entry file, with the .json extension (lowercase),
    • the external signature of the file, with the .sig extension (lowercase).
  5. The file name part of both files must match the aforementioned encoded owner public key, up to character case (all lowercase).

  6. The external signature file must be a ed25519 signature of the content of the metadata JSON file.

  7. The ticker and owner must be unique in the registry.

  8. Contents of the JSON file:

    1. Must be a JSON object, reasonably (non-offensively) formatted,
    2. Must satisfy the following JSON-schema:
    {
      "title": "Stake-pool Metadata",
    
      "type": "object",
    
      "additionalProperties": false,
    
      "required": [
        "owner",
        "name",
        "ticker",
        "homepage",
        "pledge_address"
      ],
     
      "properties": {
        "owner": {
          "type": "string",
          "format": "bech32",
          "pattern": "^ed25519_pk1[qpzry9x8gf2tvdw0s3jn54khce6mua7l]+$",
          "maxLength": 70
        },
    
        "name": {
          "type": "string",
          "minLength": 1,
          "maxLength": 50
        },
    
        "description": {
          "type": "string",
          "minLength": 1,
          "maxLength": 255
        },
     
        "ticker": {
          "type": "string",
          "minLength": 3,
          "maxLength": 5,
          "pattern": "^[A-Z0-9]{3,5}$"
        },
     
        "homepage": {
          "type": "string",
          "format": "uri",
          "pattern": "^https://"
        },
     
        "pledge_address": {
          "type": "string",
          "format": "bech32",
          "pattern": "^addr1[qpzry9x8gf2tvdw0s3jn54khce6mua7l]+$",
          "maxLength": 64
        }
      }
    }

Step-by-Step Guides

See Wiki.

incentivized-testnet-stakepool-registry's People

Contributors

2percentpools avatar admin-cf-2 avatar alphapool avatar alwswn avatar an7hrax93 avatar bigpey avatar cardanohawaiipool avatar carlwhiston avatar cf-stevew avatar cinnl avatar crptmppt avatar cryptoactif avatar cryptoblocks-pro avatar heisenbergthe3rd avatar jscsjscs avatar keynobase avatar kincraw avatar ktorz avatar lunarpool avatar maneav avatar matthaus000 avatar otaku-pool avatar redoracle avatar rickymac68 avatar smurf123444 avatar tomtom000 avatar utkusonmez avatar valuepool avatar vetro7 avatar wpoosanguansit avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

incentivized-testnet-stakepool-registry's Issues

Stake Pool Node Crashing

Dec 24 20:51:28.253 ERRO Error while accepting connection on 0.0.0.0:3000: Os { code: 24, kind: Other, message: "Too many open files" }, task: network
Dec 24 20:51:28.255 INFO service finished with error, task: network
Dec 24 20:51:28.255 CRIT Service has terminated with an error

Signature Validation failed

have tried submitting pull requests multiple times and keep getting signature validation failed

execute the following in powershell

cls
Set-Location E:\Testnet\jormungandr

.\jcli.exe key generate --type ed25519 | tee owner.prv | .\jcli.exe key to-public > owner.pub

.\jcli.exe address account --testing --prefix addr $(cat owner.pub) > owner.addr

create the .json file as
{
"owner": "ed25519_pk1yeyj2jwskjkcd3h8zllj33mglskgg5qkq0mdq4khnclc8xywap3qyen8kf",
"name": "ChampADA Stake Pool",
"ticker": "CHAMP",
"homepage": "https://champada.io",
"pledge_address": "addr1s5nyjf2f6z62mpkxuutl72x8dr7zepzszcpld5zk670rlquc3m5xysvm4zc"
}

.\jcli.exe key sign --secret-key .\owner.prv --output "ed25519_pk1yeyj2jwskjkcd3h8zllj33mglskgg5qkq0mdq4khnclc8xywap3qyen8kf.sig" .\ed25519_pk1yeyj2jwskjkcd3h8zllj33mglskgg5qkq0mdq4khnclc8xywap3qyen8kf.json

FAQ: How do I remove my Pool From The Chain

A lot of pool operators that seem to think that in order to remove their pools from the chain, they have to remove their metadata from the registry.

The Foundation has no power to retire pools from the chain, only their owners can do it. Furthermore, this registry only holds metadata about pool owners. Pool registrations however are recorded on the blockchain and are therefore subject the same laws of immutability than the rest.

Pool retirement require an explicit retirement certificate to be submitted on chain. This isn't yet supported through jcli so it could quite unpractical. However if no one delegates to a pool, it won't be elected as a slot leader and will not attract a lot of stakeholders.

If however you still want your pool to be removed from the chain, please seek help on the official Jörmungandr repository: https://github.com/input-output-hk/jormungandr/issues

⚠️ Disclaimer ⚠️

Remember that in order to help you better, the team will need to understand / have:

  • What your problem is, what are you trying to achieve.
  • What would you expect from the software / tools you're using
  • What issue / impediment are you facing
  • Which version(s) of the software are you using
  • Extra details about your operating system
  • An indication of your proficiency and expertise of the topic

Keep creating orphan Blocks...

Issue: Since moving to 8.5, I've created 4/6 orphan blocks due to blocks which did not make it into the blockchain. I then moved back to 8.4 using same config and orphaned 1 more block. I don't understand what's going on.

Examples:
2019-12-24T17:20:10.758775250+00:00"
enclave_leader_id: 1
finished_at_time: "2019-12-24T17:26:29.018736771+00:00"
scheduled_at_date: "10.39986"
scheduled_at_time: "2019-12-24T17:26:29+00:00"
status:
Block:
block: 9aad032a67592861e765e0f764907a844d79fa74c3d067f344544e4e4d096365
chain_length: 36732
wake_at_time: "2019-12-24T17:26:29.001905758+00:00"

created_at_time: "2019-12-24T03:34:21.423650054+00:00"
enclave_leader_id: 1
finished_at_time: "2019-12-24T03:41:21.017944194+00:00"
scheduled_at_date: "10.15232"
scheduled_at_time: "2019-12-24T03:41:21+00:00"
status:
Block:
block: 9202faafb863ba1437c1433a3163c1f8216f46d145978a0514825236d07a6031
chain_length: 35006
wake_at_time: "2019-12-24T03:41:21.001702587+00:00"

This one happened when I switched back to v0.8.4

  • created_at_time: "2019-12-24T18:27:38.627432484+00:00"
    enclave_leader_id: 1
    finished_at_time: "2019-12-24T18:41:43.016877296+00:00"
    scheduled_at_date: "10.42243"
    scheduled_at_time: "2019-12-24T18:41:43+00:00"
    status:
    Block:
    block: 8af8abc91f17ade8b40f5b1b2e1a0177d05484bc39efc11cac6ac557ceff3ba9
    chain_length: 36900
    wake_at_time: "2019-12-24T18:41:43.001534605+00:00"

Here's my config:
{
"log": [
{
"format": "plain",
"level": "info",
"output": "stderr"
}
],
"storage": "./storage/",
"p2p": {
"public_id": "2b7de67fdb977089bb315cb812f3332db44562a45a0a54be",
"topics_of_interest": {
"blocks": "high",
"messages": "high"
},
"max_connections": 512,
"max_unreachable_nodes_to_connect_per_event": 15,

"trusted_peers": [
{
    "address": "/ip4/13.56.0.226/tcp/3000",
    "id": "7ddf203c86a012e8863ef19d96aabba23d2445c492d86267"
},
{
    "address": "/ip4/54.183.149.167/tcp/3000",
    "id": "df02383863ae5e14fea5d51a092585da34e689a73f704613"
},
{
    "address": "/ip4/52.9.77.197/tcp/3000",
    "id": "fcdf302895236d012635052725a0cdfc2e8ee394a1935b63"
},
{
    "address": "/ip4/18.177.78.96/tcp/3000",
    "id": "fc89bff08ec4e054b4f03106f5312834abdf2fcb444610e9"
},
{
    "address": "/ip4/18.182.115.51/tcp/3000",
    "id": "8529e334a39a5b6033b698be2040b1089d8f67e0102e2575"
},
{
    "address": "/ip4/18.184.35.137/tcp/3000",
    "id": "06aa98b0ab6589f464d08911717115ef354161f0dc727858"
},
{
    "address": "/ip4/3.125.31.84/tcp/3000",
    "id": "8f9ff09765684199b351d520defac463b1282a63d3cc99ca"
},
{
    "address": "/ip4/3.125.183.71/tcp/3000",
    "id": "9d15a9e2f1336c7acda8ced34e929f697dc24ea0910c3e67"
},
{
    "address": "/ip4/52.9.132.248/tcp/3000",
    "id": "671a9e7a5c739532668511bea823f0f5c5557c99b813456c"
},
{
    "address": "/ip4/52.8.15.52/tcp/3000",
    "id": "18bf81a75e5b15a49b843a66f61602e14d4261fb5595b5f5"
},
{
    "address": "/ip4/13.112.181.42/tcp/3000",
    "id": "52762c49a84699d43c96fdfe6de18079fb2512077d6aa5bc"
},
{
    "address": "/ip4/3.125.75.156/tcp/3000",
    "id": "22fb117f9f72f38b21bca5c0f069766c0d4327925d967791"
},  
{
    "address": "/ip4/3.124.116.145/tcp/3000",
    "id": "99cb10f53185fbef110472d45a36082905ee12df8a049b74"
}
]

},
"rest": {
"listen": "127.0.0.1:59649"
},
mempool:{
"fragment_ttl": "2h",
"log_ttl": "24h",
"garbage_collection_interval": "2h"
}
}

I/O error: stream did not contain valid UTF-8

When running step 4 "Sign it using your owner private key". I got the following error.
I/O error |-> stream did not contain valid UTF-8

Guess it has something to do with the json file. But my text editor confirmed it was UTF-8. Also tried UTF-8-BOM and changing the EOL between Windows en Linux. All without luck.
Here's my json file:
{ "owner": "ed25519_pk1usgfv24ty27qzs755zqtjkfcuh8m7hxkzmh64tl3s6ge2pk9yg8qf0zv7j", "name": "ADA Straking Zone", "ticker": "ASZ", "homepage": "https://strikingsoftware.nl/ada/", "pledge_address": "addr1qhjpp9324v3tcq2r6jsgpw2e8rjul06u6ctwl2407xrfr9gxc53qulr4kt0" }

Also doing this from a Windows machine.

Automated Test Fails - QIXX

The automated check fails for my PR with "signature verification failed".

Screen Shot 2019-12-22 at 3 35 33 pm

I have tried recreating the signature file using JCLI, but get the same (so didn't see the point of pushing the file again).

I will need additional information regarding why the verification failed when I have followed the process described in the documentation.

Stakepool registration on Pending for long time (30+ mins)

stakepool_id: b6392fcd8279cf56d774cf130c801ba526256322fa62a2f642036d82a42042fc
account_address: ca1skehj4q3acs6x0a4zyu6qf4uyq22yccueqcggz947pc539jhfrv4j72azjv

- fragment_id: 9d9b663ddda6127c177a01aa83a2077b62a99e87fc3e1fa9320e8cdb0d32b9d6 last_updated_at: "2019-12-15T08:44:28.271794080+00:00" received_at: "2019-12-15T08:44:28.271794007+00:00" received_from: Rest status: Pending

tx_id: 31a29906a7bc0b4182ed4ba0c59ff349a40bcb15f3f2cadba92a128fadf893b6

This is blocking my stakepool registration. Because if I create a new stakepool registration it'll us ehe same fragment_id and transaction_id I think it's just seeing the message on the bus already and ignoring a re-register. Not sure what todo atm

here is the account
https://shelleyexplorer.cardano.org/en/address/ca1skehj4q3acs6x0a4zyu6qf4uyq22yccueqcggz947pc539jhfrv4j72azjv/

Stakepool BKIND not being selected as leader

Hi,

In the community I mentioned my stake-pool, ticker name BKIND, has not been selected yet as a leader. Based upon advice given by one of the community members, I would like to request the K=100 parameter to be changed to K=500 for my pool: BKIND. Can this be done?

With kind regards,
Gertjan

Unable to check balance of the address.

I am creating a stake pool and am having the following error when i try to check the balance of my stake pool account.
failed to make request.
failed to make a REST request
|-> node rejected request because of invalid parameters
|-> http://127.0.0.1:3100/api/v0/account/4b213361b6ca1b653fb96289ebcfd31c5e61c245d9db95826063a42edf6492f3: Client Error: 404 Not Found

The command i am executing is.
ADD=addr1s49jzvmpkm9pkeflh93gn6706vw9ucwzghvah9vzvp36gtklvjf0xjzgcnp
jcli rest v0 account get $ADD -h http://127.0.0.1:3100/api

FAQ: How do I update / delete my metadata in the registry

Removing metadata from the registry is an ad-hoc process. If this was allowed without verification, anyone could delete metadata of anyone. Therefore, there are two cases:

I need to update my metadata and my private/public owner keys are the same.

Then, the procedure is the same as for registering new metadata:

  • Update your JSON file
  • Produce a new signature that will replace the existing one
  • Submit a pull request

I need to register different private/public owner keys but I want to keep the same ticker.

Here, you'll have to make two pull requests:

PR A

  • Update your previous registration's ticker to VOID + a number that isn't currently taken (e.g. VOID2).
  • Produce a new signature to replace the existing one
  • Submit a pull request
  • Make sure to indicate your previous PR as a comment of that PR and explicitely mention that you are voiding this registration and want it to be deleted.

PR B

  • Create a new registration re-using your previous ticker
  • Name it after your new public key
  • Submit a pull request
  • Make sure to mention your "void PR" as a comment so that it's clear.

This PR will fail to pass CI until the first one is merged. This is normal.

My pull requests has not been merged yet. Why?

Remember that pull requests are managed by humans and we are doing our best to make this a diligent process. Requests are treated from the oldest first; please do not ping administrator of this repository directly in issues and be patient 🧘‍♂️.

ADPL Pool is not showing in Yoroi Shelly testnet extension

Dear Team,

i am a pool operator and my stake pool name " ADAdarkpool " Ticker - ADPL.

I am able to see my pool ADPL in Daedalus rewards TNv1 however unable to see it from Yoroi shelly testnet brave browser extension. Could you please advise if am missing anything.

All my test ADA is in Yoroi shelly testnet brave browser extension so currently am unable to stake my own test ada to my pool to see the performance. please advise.

Thanks,
karthik

Step Two: "passphrase is too short"

Hi,
I'm on step two of migrating a byron wallet to shelley wallet.
I didn't use a passphrase when I created it. When I run the command using the following
"passphrase": "",

I get this error:

{"code":"bad_request","message":"Error in $.passphrase: passphrase is too short: expected at least 10 characters"}

If i try removing the parameter completely, I get this error. Feels like a catch-22
{"code":"bad_request","message":"Error in $: key 'passphrase' not present"}

How do you migrate a byron wallet that wasn't created with a passphrase?

Stakepool registration on Pending for long time (30+ mins)

stakepool_id: b6392fcd8279cf56d774cf130c801ba526256322fa62a2f642036d82a42042fc
account_address: ca1skehj4q3acs6x0a4zyu6qf4uyq22yccueqcggz947pc539jhfrv4j72azjv

- fragment_id: 9d9b663ddda6127c177a01aa83a2077b62a99e87fc3e1fa9320e8cdb0d32b9d6 last_updated_at: "2019-12-15T08:44:28.271794080+00:00" received_at: "2019-12-15T08:44:28.271794007+00:00" received_from: Rest status: Pending

tx_id: 31a29906a7bc0b4182ed4ba0c59ff349a40bcb15f3f2cadba92a128fadf893b6

This is blocking my stakepool registration. Because if I create a new stakepool registration it'll us ehe same fragment_id and transaction_id I think it's just seeing the message on the bus already and ignoring a re-register. Not sure what todo atm

ERRO cannot schedule pulling headers

The following console messages like below appear frequently:

Jan 04 16:50:10.383 ERRO cannot schedule pulling headers, reason: failed to send a command: channel closed, from_node_id: a74ecf0adc8955e44fb5266c69eec7fb3ccb3a8a4a57535e, date: 21.36969, parent: e7cb5ab79c962f2c3172860ecaec4f4851edac1c1b082340a0b53b5f4c75ba38, hash: aa53bea89d257e3e184e655485bf0f1ceb124c93374b7377c447d6d9fba3b050, task: block

Running on 0.8.5 (stakcepool) with the trusted peers for ITN Rewards.

Step 4: Migrate your Byron wallet: "method_not_allowed"

Executing Step 4 of the documentation results in an error. Steps 1-3 were successful

$ curl -X POST http://127.0.0.1:8090/v2/byron-wallets/$BYRON_ID/migrations/$SHELLEY_ID \
  -H "Content-Type: application/json" \
  -d '{
    "passphrase": "SOME PASSWORD"
  }'

{"code":"method_not_allowed","message":"You've reached a known endpoint but I don't know how to handle the HTTP method specified. Please double-check both the endpoint and the method: one of them is likely to be incorrect (for example: POST instead of PUT, or GET instead of POST...)."}

buildkite- error: couldn't create a temp dir

I have created a pull request commit 570b408 - ADAPT #336
Getting error in the buildkite job:
error: couldn't create a temp dir: No such file or directory (os error 2) at path "/build/jormungandr-cli-0.8.0-rc1+-source/target/debug/deps/rmeta5ddhob"

error: aborting due to previous error

error: Could not compile jcli.
warning: build failed, waiting for other jobs to finish...
thread '' panicked at 'src/librustc_codegen_ssa/back/write.rs:1545: worker thread panicked', src/librustc/util/bug.rs:37:26
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
error: could not write output to /build/jormungandr-cli-0.8.0-rc1+-source/target/debug/deps/jcli-3ecc76dce50d15c0.3237eel1oitwxl84.rcgu.o: No such file or directory

error: aborting due to previous error

error: Could not compile jcli.

Is this related to my commit? How can I fix this? Thanks

Delete ALOHA pool --- need to recreate

Please delete the ALOHA pool that I made and has been merged. The public key is incorrect to match with my pool on the ITN. I will resubmit a new pull request with new json and sig files once it's gone. Thanks.

How to move delegated amount back to rewards wallet?

How to move delegated amount back to new wallet?

I have delegated ADA to my own stake pool. I want to move my ada back to my new rewards wallet (or back to balance wallet) as my stake pool is not listed in Daedalus. After this I want delegate to another pool and turn off my own. How to do it?

Node ID:201e9f71df730e2b3a8336eaf1a202caa8c4befa3db349d9d90d4c93ae81487d
jcli jormungandr v0.8.2

Thanks

Duplicate ticker fix

I'm not trying to over post this issue, but the PR thread is a mess and I'm sure it is a full time job keeping up with it. We need the automated checks to be either updated or a solution to the issue of changing already merged files ( #24 ).

As you can see in my attempts to get #337 to pass the auto checks. I have tried this many ways, uploading 2 new files so that it only changes 2 files, fails due to "duplicate ticker"even though it is myself trying to update the info. These are running in to this issue as well here #384 #355 I'm sure I missed some, #360 was able to pass for now, it was brought from a fork that is 788 commits behind, so once you merge in master it will fail for "duplicate ticker".

I have also tried only changing the files that need to be changed. However doing so is looked at like 3 files being changed. This is bc the public key (file name) is being changed which normally would just look like a change. However the only other part of that file is the sig and it to is being changed, so this is looked at like a new file rather then changing one already merged. If there was more lines to the sig file or it was not labeled with the public key this wouldn't happen this way. I understand they need to be this way, so we will just need a solution moving forward for everyone that needs to update information like this.

Migrated Funds Not Available

I have migrated funds from my Byron to my Shelley wallet. I have confirmed their status via

cardano-wallet wallet get $ShelleyID
and
cardano-wallet transaction list $ShelleyID

However, when using jcli to get account
.\jcli.exe rest v0 account get $Addr -h http://127.0.0.1:3101/api
the returned values are 0
counter: 0
delegation:
pools: []
last_rewards:
epoch: 0
reward: 0
value: 0

Logs shows - OS ERROR 110

Dear Team,

I am receiving lots of OS error in my node ADPL - Ubuntu - hosted in VPS.

Need help and advise to solve this error.

Thanks,
karthik

SAND Metadata Doesn't Show in Shelly Explorer

I've raised this with IOHK support desk however they just refer me to the online community and this GitHub repo. Not convinced its the right place for it but here goes anyway.

SAND pool does not show its registered metadata in the Shelly Explorer:

https://shelleyexplorer.cardano.org/en/stake-pool/03a01cb9acffb3374c9a86ff39b2b5d85128c9ce3ac3fdba51ceceaca0685f98/

The pool is correctly registered. The pool is operating perfectly. The pool is producing blocks.

FAQ: Why is my pool listed twice or thrice in Daedalus?

A. The registry is about pool OWNERS

One important thing to keep in mind is that, in this registry are registered metadata about pool owners (identified via their owner public key). However, a single owner may have multiple pools. Should several pools be registered on chain with the same owner, they'll all show up in Daedalus with the same metadata!

B. Old pools have to be retired

Register a new pool on the chain with the same owner doesn't automatically void the previous registration you did with that owner key. As a pool operator, you need to explicitly retire your old pools if you want them removed from the listing.
The creation of retirement certificate is not yet supported by jcli but should be available soon. Please, refer to the official repository for any matter or help regarding pool retirement: https://github.com/input-output-hk/jormungandr.

I can't execute the createStakePool.sh script

The following error occurs in the output of StakePool.sh script.
I couldn't get Stake Pool ID.
Could you tell me how to solve it?

4.3 Execute the createStakePool.sh script
https://github.com/input-output-hk/shelley-testnet/blob/master/docs/stake_pool_operator_how_to.md

jcli 0.8.5-alpha1
jormungandr-v0.8.5-alpha1

~$ ./createStakePool.sh 3100 10000 1/20 1000000 $ed25519e_sk×××××××××××××× |tee createStakePool_output.txt
invalid Bech32
  |-> invalid length
error: The following required arguments were not provided:
    <PUBLIC_KEY>
USAGE:
    jcli address account <PUBLIC_KEY> --prefix <prefix> --testing
For more information try --help
================ Blockchain details =================
BLOCK0_HASH:  9409af111b04896c756c1cee3b7f9bae8b9ed1843c9e0a5f07d92ab9b62f6f78
REST_PORT:    3100
TAX_VALUE:    10000
TAX_RATIO:    1/20
ACCOUNT_SK:   1000000
==================================================
 ##1. Create VRF keys
POOL_VRF_SK: vrf_sk××××
POOL_VRF_PK: vrf_pk××××
 ##2. Create KES keys
POOL_KES_SK: kes25519-12-sk1××××××××××××××××
××××××××××××××××××××××××××××××××××××××××
POOL_KES_PK: kes25519-12-pk1××××××××××××××××××××××××××××××××××××××××
 ##3. Create the Stake Pool certificate using above VRF and KEY public keys
error: The argument '--owner <OWNER_KEY>...' requires a value but none was supplied
USAGE:
    jcli certificate new stake-pool-registration --kes-key <KES_KEY> --owner <OWNER_KEY>...
 --start-validity <SECONDS-SINCE-START> --tax-ratio <TAX_RATIO> --tax-fixed <TAX_VALUE> --m
anagement-threshold <THRESHOLD> --vrf-key <VRF_KEY>
For more information try --help
 Sign the Stake Pool certificate
Invalid certificate
  |-> expected certificate in bech32
  |-> invalid length
cat: stake_pool_certificate.signed: No such file or directory
SIGNED_STAKE_POOL_CERTIFICATE: 
 ##4. Send the signed Stake Pool certificate to the blockchain
===============Send Certificate=================
CERTIFICATE_PATH  : stake_pool.cert
REST_PORT         : 3100
ACCOUNT_SK        : 1000000
BLOCK0_HASH       : 9409af111b04896c756c1cee3b7f9bae8b9ed1843c9e0a5f07d92ab9b62f6f78
FEE_CONSTANT      : 200000
FEE_COEFFICIENT   : 100000
FEE_CERTIFICATE   : 10000
FEE_CERTIFICATE_POOL_REGISTRATION:  500000000
FEE_CERTIFICATE_STAKE_DELEGATION :  400000
==================================================
invalid Bech32
  |-> invalid length
 ##5. Retrieve your stake pool id (NodeId)
Invalid data
  |-> invalid length
============== Stake Pool details ================
Stake Pool ID:    
Stake Pool owner: 
TAX_VALUE:        10000
TAX_RATIO:        1/20
==================================================
rm: cannot remove 'stake_pool_certificate.signed': No such file or directory
 ##6. Create the node_secret.yaml file

I already created stakepool_owner_account.txt(PRIVATE_KEY_SK,PUBLIC_KEY_PK,ADDRESS).

Create stake pool issues

Hi,

Using jormungandr v0.8.3-8f276c0

I followed the instructions to create a stake pool:
https://github.com/input-output-hk/shelley-testnet/blob/master/docs/stake_pool_operator_how_to.md#create-an-account-address-using-the-script

I run last version of the script:
curl -sLOJ https://raw.githubusercontent.com/input-output-hk/jormungandr-qa/master/scripts/createStakePool.sh
curl -sLOJ https://raw.githubusercontent.com/input-output-hk/jormungandr-qa/master/scripts/send-certificate.sh

Result:

 ##11. Remove the temporary files
  ##Waiting for new block to be created (timeout = 200 blocks = 400s)
New block was created - 2ab06d115c84d6148f6c5a79b701597d4b05b8f3e4471f253dea7679f979cae3
 ##5. Retrieve your stake pool id (NodeId)
7e410dd40ccdf1170840029cc8e6599e0ce86886f3224d7f0c90914759f5e40b
============== Stake Pool details ================
Stake Pool ID:    7e410dd40ccdf1170840029cc8e6599e0ce86886f3224d7f0c90914759f5e40b
Stake Pool owner: [hidden]
TAX_VALUE:        10000
TAX_RATIO:        1/10
==================================================
 ##6. Create the node_secret.yaml file

The block has been created
https://shelleyexplorer.cardano.org/en/block/2ab06d115c84d6148f6c5a79b701597d4b05b8f3e4471f253dea7679f979cae3

The stake pool id "7e410dd40ccdf1170840029cc8e6599e0ce86886f3224d7f0c90914759f5e40b" does not exist in the list

./jcli rest v0 stake-pools get --host "http://127.0.0.1:3100/api"

OR

./jcli rest v0 stake-pool get $STAKEPOOL_ID --host "http://127.0.0.1:3100/api"
failed to make a REST request
|-> node rejected request because of invalid parameters
|-> http://127.0.0.1:3100/api/v0/stake_pool/7e410dd40ccdf1170840029cc8e6599e0ce86886f3224d7f0c90914759f5e40b: Client Error: 404 Not Found

how come the node-id does not appear?
Thanks

Node Crash Error while accepting connection on 0.0.0.0:3000

Dec 25 00:51:54.563 INFO connecting to peer, node_id: d91ef2ed737f4ada7c648265d16478414f1eaa6fd2108cff, peer_addr: 85.25.159.219:3000, task: network
Dec 25 00:51:54.572 ERRO Error while accepting connection on 0.0.0.0:3000: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }, task: network
Dec 25 00:51:54.573 WARN response canceled by the processing task, request: UploadBlocks, sub_task: server, task: network
Dec 25 00:51:54.573 WARN response canceled by the processing task, request: UploadBlocks, sub_task: server, task: network
Dec 25 00:51:54.575 INFO service finished with error, task: network
Dec 25 00:51:54.576 CRIT Service has terminated with an error
A service has terminated with an error

My pool is listed three times in Daedalus

Bildschirmfoto 2019-12-17 um 04 22 22

My pool KNTI is currently listed three times in Daedalus (currently ranked 9, 224, and 255). I had initially listed is under the ticker KTI and did not know how to update it after they were already merged.

Please delete the registrations under the ticker for KTI.

Please keep my active pool KNTI has a pool id of 6f23b9a72c6123b485594cc27dfc67ac870004135ee2286b92a05b592a52307cand the owner ed25519_pk1tjqcnwvuwzxs84d4j45czrmjvzkpvkspfqhctnlhgtvdvk5vu2wq2tx4hp.

Remove request from stake pool list

The stake pool below is always offline.

Please remove it from the stake pool list in the daedalus. (invisible)

pool ID : 47717c4823ef864eee3449a52c9d2d29c20c35e757d176634d73fa2fd4847053

Registering a new pool with same owner: Daedalus duplicates but Yoroi does nothing

It has been talked earlier in #727 that Daedalus doesn't remove the old registration done with the owner key and displays the search like this:

daedalus

This is not a big issue as the older one eventually starves and goes down the list, while the currently online one goes up. However, the real issue lies in Yoroi wallet:

yoroi

It is ONLY displaying the older one, and not updating to the newer registration.

Missing instructions for migrating byron wallet

Hi,

i am following the registration instructions - in the prerequisites there is a mention of migrated wallets.

Have your Daedalus wallet 15-word mnemonic ready. Only migrated wallets can be used in the steps described below. Old Byron wallets need to be migrated first.

My test wallet on Daedalus passed all balance checks pre and after snapshot, but i don't have a 15 word mnemonic, only a 12 word one.
If there are steps to migrate wallets on the testnet, manually, i could not find them (i suppose using cardano-wallet migrate would be an option?)

It would be helpful to have an authoritative answer on how to do the migration, since it blocks pool registration for anyone with an older wallet.

If pointed to a correct doc, i can prepare the PR :)

Remove pool or wrong ticker from chain

When registering the pool I have adjusted the fee several times... with the same ticker. it is possible to remove the 2 wrong tickers. Since there is only a physical pool and the other 2 doing nothing but are still visible.

Daedalus ITN not showing my ticket pool

Hello,

The pool is registered in the blockchain and can be see in the shelley explorer searching by id (f9ae8a75c3256beeed42285a0be0351ef2b8cedd2f916f2aef71b9219892a8ae).

Follow this, i done the pull request for make my pool/ticket visible in Daedalus Rewards (pr #1261 - ef7b59f).

The problem is that the pr seems ok and merged, but the pool/ticket is not showing in Daedalus Rewards.

Any idea? Thanks!!!

Pool id is not listed when I check with jcli

I did all steps discribed at the most recent docs https://iohk.zendesk.com/hc/en-us/articles/900000038626, but the verification for my pool id at step 4.4 (4.4 Check that the stake pool is in the blockchain.) seems to fail

$ cat createStakePool_output.txt

[...]
 ##11. Remove the temporary files
  ##Waiting for new block to be created (timeout = 200 blocks = 400s)
New block was created - 0c4b6e16ce44c4d6cdc6d78994f66052b5b6aeb5539420c810a922dcaa2fec9d
 ##5. Retrieve your stake pool id (NodeId)
a78d7c2d59805db899d3ce03e4d0673cbe2e623790e1e0637dc22f0a52bdada0
============== Stake Pool details ================
Stake Pool ID:    a78d7c2d59805db899d3ce03e4d0673cbe2e623790e1e0637dc22f0a52bdada0
Stake Pool owner: ca1s54cflndqnvljq49e70pkueqa4qua6l8ewcfj3qj5jtzvg02kukag7gq4rl
TAX_VALUE:        750000
TAX_RATIO:        1/20
TAX_LIMIT:        0
==================================================
 ##6. Create the node_secret.yaml file

But my pool is not listed when I check it like this:

$ jcli rest v0 stake-pools get -h "http://127.0.0.1:3100/api" | grep a78d7c2d59805db899d3ce03e4d0673cbe2e623790e1e0637dc22f0a52bdada0
$

=> NO OUTPUT => the genrated stake pool id I created in advance is missing.

Both of jormungandr and jcli is an binary version of release 0.8.0.

So whats going wrong? How can I verify that all is working now?
Thanks in advance.

request pool has been validated/delageted epoch 1 but pool but it is not visible with the command jcli epoch 2

hello

saturday "epoch 1" , my request has been validated #499

i delegated ada to my pool

jcli rest v0 account get $ ADDR -h http://127.0.0.1:3100/api
.............................
pools:
- - f756c8f3e31bd56bd01c569e6a130cd9026ee69a90c329374dedf42e3ee01e12
- 1
last_rewards:
epoch: 0
reward: 0
value: 1098300000

But my pool does not appear with the command jcli rest v0 stake get --host "http://127.0.0.1:3100/api" => epoch2
But my pool is visible on https://shelleyexplorer.cardano.org/en/stake-pool/f756c8f3e31bd56bd01c569e6a130cd9026ee69a90c329374dedf42e3ee01e12/

How to know if my pool is really functional ?

Get the "pledge_address"

Can't find a way to get the pledge_address;
The manual says:

❓ The pledge_address can be any valid address you own. However, we recommend using the account address corresponding to your Daedalus or Yoroi assigned reward account. This account may also be used to fund your registration certificate for your stake pool.

But my address in Daedalus has uppercase characters in it.

Get the owner key

The manual sas:

⚠️ If you want to be able to monitor your rewards inside Daedalus or Yoroi, make sure to derive your owner public key from your mnemonic sentence at the right derivation path (e.g m/1852'/1815'/0'/2/0).

But how would someone do that?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.