babylonchain / networks Goto Github PK

View Code? Open in Web Editor NEW

21.0 3.0 283.0 1.11 MB

Standard ML 45.88% Shell 9.40% Go 44.72%

networks's People

Contributors

Stargazers

Watchers

Forkers

fcpidz213 gumbolover itrocket-team amit0080 mrcryptooo rudikserz1971 tudor1217 addicola kwunyeung bwarelabs upnodedev meria-finance dc982 kinrokinro nodesguru daicers curlycrypto184 ghazni101 ramadii maaaagi hakailuganodes pro-delegators mkruby009 green-edge nemca mnguyen-io puckapao staking4all duccas chadwick2143 choihocheol hairtail stakeandrelax-validator heyapplemango chorusone leverfi-ops mattketmo errorist79 kimheeje12 simon-provalidator vaddec-everstake zenon-provalidator hashkeycloud 0xmakase vsea enigma-validator wyh48 littlebodhi wheniamyoung lisasilva2253 hiangelajohnson aaronstewards kcharlescochran engwon nodeinfra whyrulike nodestake stevenlee7 meetrick gnongs devopsjetking romarioext rickychez ulikestyle stakinofficial renderlynx tlanderon bitscale-dev mattwhew devinhpbr validatorfm archmsc ytochkaaa alezz1x aalahyane95 victorosipchuk dremling calvinjolly nihilsupernum cosmos-spaces andromeda-node carolinier nate-staked xtraktd polkachuintern jinnzy danielimkk alt-research ivy191118 gentlemenvalidators tesodeall clemensgg jason2d2 liewhite wilsonf2pool dim-dora mllnd blockhunters-dev ajvpot bill-git1

networks's Issues

Add CI parameters updates

On phase 1 registry of parameters, add CI to verify updates

FP Registry Improvements

Make security contact mandatory in guide and CI check
After signing the transaction you should have it in hex format. some people missed the signing part because the relevant instructions are in the other page. It would be good if we stress the tx hex should be signed (we have a placeholder tx hex in the upper example which is not signed, which is confusing)
curl https://bitcoin-testnet-archive.allthatnode.com/ this website is not stable and people often get curl: (6) Could not resolve host: bitcoin-testnet-archive.allthatnode.com. Maybe we can choose another one that is stable? And, people also got confused about performing this step event after the successfully submitted their tx via bitcoin-cli sendrawtransaction. So, it’s better to stress that we recommend submitting the signed tx by running bitcoind node locally and using bitcoin-cli sendrawtransaction to submit tx. For those they don’t want to run a bitcoind node they can choose a third part endpoint but it requires trust and they can be not stable
when creating finality provider information object, it is confused to have "btc_pk": "<eots_btc_pk>", many people thought this is the staker pk because we use --finality-provider-pk=<fp_pk> in the other place. So it would be less confusing if we make it consistent (eg "finality_provider_pk"=<finality_provider_eots_pk>)
if user has installed the staker-cli v0.2.0, then ./bbn-test-4/finality-providers/scripts/fp-check-tx.sh would fail as staker-cli 0.2.0 does not support the min-staking-amout flag in staker-cli transactions check-phase1-staking-transaction. So better to make a new release of staker-cli and ask user to use the correct version.

Could you please tell me if the submitted Fp will appear in the next test environment

Hello, I found that the FP code I submitted has been merged into the main branch, but I did not find my FP in the list in the test environment. Could you please tell me if it will appear in the next test environment，thanks！

have no permission to push the json and sig configure file to bbn-test-4

Hi， According to the documentation you provided, I have deployed bbn-test-4 finality-provider locally。but when i push the json and sig configure file to bbn-test-4, the git tell me no permission, I switched to my colleague's account and encountered the same problem.Can you tell me how to apply for this permission? Or give me an invitation, thanks!

Collect PR failures data on finality provider registration to improve guide

Gather information about PR's failures to create action items and improve finality provider registration guide

Failures

1. Signed json is not exactly the same

The json file with the finality provider registration info is used to generate a signature with eotsd sign-schnorr and when the PR is open instead of using the same file, just the content is being pasted to Git Hub.

Cases: #29, #47, #55, #59, #66, #67, #72, #74, #75, #85 .. #92, #125, #133, #147, #157, #166, #188

Add explicit instruction to use the same file signed to open the pull request in the guide

2. Bad covenant-comittee-pks

The covenant-comitte-pks used is not the lock only specified in the guide, but rather used the example on the docs for btc-staker

Cases: #31

Create a commit on reference repositories with examples that match the values recommended in the registry guide.

3. Diff fp pk tx and file

The finality provider public key specified in the registration file does not match the one used to create the transaction

Cases: #77, #152, #156, #165

Create a commit on reference repositories with the example that uses <fp_pk> as instruction instead of the example fp_pk as it can confuse the user

4. Staking amount different than required

The lock amount set on the tx was different than the one specified. If the specified amount is higher, all good, the registration can proceed, if it is lower than the specified it needs to create the deposit transaction again.
Cases: #39, #58, #62, #107

Higher already solved by using flag of --min-staking-amount on the verification
Lower, we need to be explicit in the guide that if it is lower than the specified it will not be a valid registration.

5. Not enough BTC confirmations

The pull request with the BTC tx self-lock deposit does not have enough confirmations
Cases: #44, #66, #113

Add script to verify the modified files if it is an FP registration, Make sure it has at least 6 confirmations

6. Did not provide a signature

The created pull request only contained the json information, missing the signature
Cases: #50

CI fail warning about missing file

7. Signature file with unexpected name

The created pull request registration had an unexpected file name like nickname.sig.tx instead of nickname.sig
Cases: #145

CI not finding the corresponding signature seems enough

Not able to connect to p2p network

Babylon : v0.7.2

I have followed the instructions and added seeds from here. The node is not being able to connect to the peers and the network.

Please check if the seeds are healthy.

I am getting these logs :

Jan 01 08:09:51 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:51 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:51 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:51 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Reconnecting to peer addr={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459} module=p2p
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl="Peer{MConn{65.109.68.190:16459} 3f472746f46493309650e5a033076689996c8881 out}" module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl=MConn{65.109.68.190:16459} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Connection is closed @ recvRoutine (likely by the other side) conn={"Logger":{"Logger":{}}} module=p2p peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Reconnecting to peer addr={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459} module=p2p
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl="Peer{MConn{65.109.68.190:16459} 3f472746f46493309650e5a033076689996c8881 out}" module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:52 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl=MConn{65.109.68.190:16459} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:53 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Connection is closed @ recvRoutine (likely by the other side) conn={"Logger":{"Logger":{}}} module=p2p peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:53 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:53 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:53 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:53 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Reconnecting to peer addr={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459} module=p2p
Jan 01 08:09:53 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl="Peer{MConn{65.109.68.190:16459} 3f472746f46493309650e5a033076689996c8881 out}" module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:53 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl=MConn{65.109.68.190:16459} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Connection is closed @ recvRoutine (likely by the other side) conn={"Logger":{"Logger":{}}} module=p2p peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Reconnecting to peer addr={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459} module=p2p
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl="Peer{MConn{65.109.68.190:16459} 3f472746f46493309650e5a033076689996c8881 out}" module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl=MConn{65.109.68.190:16459} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Connection is closed @ recvRoutine (likely by the other side) conn={"Logger":{"Logger":{}}} module=p2p peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:54 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Reconnecting to peer addr={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459} module=p2p
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Error reconnecting to peer. Trying again addr={"id":"4b1f8a774220ba1073a4e9f4881de218b8a49c99","ip":"3.136.177.195","port":26656} err="auth failure: secret conn failed: read tcp 143.198.50.225:40574->3.136.177.195:26656: i/o timeout" module=p2p tries=17
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl="Peer{MConn{65.109.68.190:16459} 3f472746f46493309650e5a033076689996c8881 out}" module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl=MConn{65.109.68.190:16459} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Connection is closed @ recvRoutine (likely by the other side) conn={"Logger":{"Logger":{}}} module=p2p peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:55 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Reconnecting to peer addr={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459} module=p2p
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl="Peer{MConn{65.109.68.190:16459} 3f472746f46493309650e5a033076689996c8881 out}" module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl=MConn{65.109.68.190:16459} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Connection is closed @ recvRoutine (likely by the other side) conn={"Logger":{"Logger":{}}} module=p2p peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Reconnecting to peer addr={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459} module=p2p
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl="Peer{MConn{65.109.68.190:16459} 3f472746f46493309650e5a033076689996c8881 out}" module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:56 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service start impl=MConn{65.109.68.190:16459} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:57 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF Connection is closed @ recvRoutine (likely by the other side) conn={"Logger":{"Logger":{}}} module=p2p peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:57 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}
Jan 01 08:09:57 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM ERR Stopping peer for error err=EOF module=p2p peer={"Data":{},"Logger":{"Logger":{}}}
Jan 01 08:09:57 ubuntu-s-4vcpu-8gb-sfo3-01 cosmovisor[17595]: 8:09AM INF service stop impl={"Data":{},"Logger":{"Logger":{}}} module=p2p msg={} peer={"id":"3f472746f46493309650e5a033076689996c8881","ip":"65.109.68.190","port":16459}

I am having trouble adding babylon testnet network to kepler?

script to validate signed `MsgCreateFinalityProvider`

Uses babylonchain/finality-provider#521

script to Generate `MsgCreateFinalityProvider` easier

Receive the FP json registration from first registration phase and some parameters to generate the signed msg

Guide Signed Msg to Create FP

Guide describing how to submit signed msg MsgCreateFinalityProvider securely for each finality provider already registered

block catch_up so slowly

my node's height up to 48000,after block catch_up so slowly
It's up to 62000 for 3days
the version is :dev-107ab1b457f7b4caef846239990fc93a23efe96a

Validate that `UnbondingFee` is lower tham `MinStakingAmount`

Parser should check that unbonding fee (https://github.com/babylonchain/networks/blob/main/parameters/parser/ParamsParser.go#L122) is lower that min staking amount https://github.com/babylonchain/networks/blob/main/parameters/parser/ParamsParser.go#L126

OOM errors

Nodes become unavailable after running for a while
looks like OOM happens

restart didn't help,pls check

The machine is configured as follows:
2C8G 800G

Unable to send transactions on bbn-test-4

Hello, our wallet has integrated Testnet 3 before. After testing, address derivation, private key generation, gas estimation and sending transactions can all work properly. Recently, we migrated from Testnet 3 to Testnet 4, but we have not found the corresponding RPC node. After changing the chain id to bbn-test-4 and using https://babylon-testnet-rpc.polkachu.com:443 as the RPC node, the following error is prompted when sending transactions:

[Error: Broadcasting transaction failed with code 4 (codespace: sdk). Log: signature verification failed; 
please verify account number (0) and chain-id (bbn-test-3): (unable to verify single signer signature): unauthorized]

Besides, we're using cosmjs to implement this. Currently, we can get account information, balance, and gas estimation normally, but we cannot send transactions. The address for testing is bbn199xewvwqmfue5r63prac0sy8apejjtux4qz434, and it's a bit strange that I can't see the account related records in the explorer now.

I hope the team can provide some guiding opinions, thank you!

Staking value could be less than unbonding fee which causes unbonding to fail

Recommend Projects

React

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

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

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

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
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.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

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

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.