-
-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulsechain Network Addition #12948
Pulsechain Network Addition #12948
Conversation
Thank you for your pull request and welcome to Unlock! We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @JexxaJ on file. |
Thanks @JexxaJ Please open another PR with the required changed to the CLA file! |
export * from './linea' | ||
export * from './sepolia' | ||
export * from './pulsechain' | ||
export * from './pulsechainTestnetV4' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We try to not add all testnets because that means we have to maintain them.
Any reason why Goerli or Sepolia are not enough?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the development that is done on pulsechain is tried and tested using pulsechain testnet as it replicates the particular way in which the system state was forked over form Eth mainnet. If possible it would be great to see it added as it will foster development using the unlock protocol.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We won't add it as it means more work for our team... if Pulsechain is not compatible with Ethereum test nets then we should not add support for it.
|
||
export const pulsechain: NetworkConfig = { | ||
chain: 'pulsechain', | ||
description: 'pulsechain mainnet.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need a better description here so users know what is specific about Pulsechain please!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will add something more detailed.
fullySubsidizedGas: false, | ||
id: 369, | ||
isTestNetwork: false, | ||
keyManagerAddress: '', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TK
isTestNetwork: false, | ||
keyManagerAddress: '', | ||
maxFreeClaimCost: 10000, | ||
multisig: '', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TK
IT looks like Gnosis Safe does not support this chain... can you please confirm?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct they have not included pulsechain on the UI, however this network is one of the biggest users of gnosis safes via
https://staker.app/ which is the UI used on pulsechain and ethereum.
The liquid loans team have deployed a cut down version of gnosis on both testnet and mainnet at the below URLs.
https://pulsechainsafe.com/
https://testnet.pulsechainsafe.com/
Let me know if you need more information on these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At this point we don't want to add more work to our team to maintain non standards setup.
symbol: 'PLS', | ||
}, | ||
previousDeploys: [], | ||
provider: 'https://rpc.unlock-protocol.com/369', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would need to deploy a provider for this.
previousDeploys: [], | ||
provider: 'https://rpc.unlock-protocol.com/369', | ||
publicLockVersionToDeploy: 13, | ||
publicProvider: 'https://scan.pulsechain.com', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a block explorer. We need an RPC endpoint here.
provider: 'https://rpc.unlock-protocol.com/369', | ||
publicLockVersionToDeploy: 13, | ||
publicProvider: 'https://scan.pulsechain.com', | ||
startBlock: 2247300, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TK
publicLockVersionToDeploy: 13, | ||
publicProvider: 'https://scan.pulsechain.com', | ||
startBlock: 2247300, | ||
// Graph can be found at https://graph.pulsechain.com/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is not a standard https://thegraph.com/ setup you need to send us docs on how to set it up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will try and get some more info for you on this side of things. Is this a nice to have or required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Required for the frontend to work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, so there is a community graph node that can be used. I have spoken to the team running this and they have advised while there is no end-user UI at present if you are able to provide the subgraph code you want hosted they will run this up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry this is too complex for us to maintain so until there is a proper graph deployment we won't merge this PR.
networkName: 'pulsechain', | ||
studioEndpoint: 'unlock-protocol-pulsechain', | ||
}, | ||
unlockAddress: '', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is incomplete. Please remove the testnet as well.
Co-authored-by: Julien Genestoux <[email protected]>
Thank you for your pull request and welcome to Unlock! We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @JexxaJ on file. |
Thank you for your pull request and welcome to Unlock! We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @JexxaJ on file. |
Co-authored-by: Julien Genestoux <[email protected]>
Thank you for your pull request and welcome to Unlock! We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @JexxaJ on file. |
Thank you for your pull request and welcome to Unlock! We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @JexxaJ on file. |
Thank you for your pull request and welcome to Unlock! We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @JexxaJ on file. |
Can you please have another look over this request and let me know if anything is still outstanding? thanks. |
Closing as stale |
Description
Issues
This PR address this issue #9304 (comment)
Checklist: