cartesi / explorer Goto Github PK
View Code? Open in Web Editor NEWCartesi Blockchain Explorer
Home Page: https://explorer.cartesi.io
License: Apache License 2.0
Cartesi Blockchain Explorer
Home Page: https://explorer.cartesi.io
License: Apache License 2.0
We noticed that unit tests take a lot of time to execute while not containing anything heavy in terms of computations.
Most of the time, those tests contain some mocks and simple checks that should be rather fast. Mocks are stored in memory and we are not calling any third-party services so the large amounts of time required for tests to execute are not justified. This also impacts our builds as they are slower than expected.
There are multiple things we can do to improve unit tests speed. An example is to optimize imports since jest (our test runner) takes more time to process large imports than specific ones.
Example from packages/ui
:
This is slower:
import { StakePlusIcon } from '../../src/components';
than this:
import { StakePlusIcon } from '../../src/components/Icons';
test:ci
command.--runInBand
flag for test:ci
. For reference - https://jestjs.io/docs/cli#--runinband.Currently, for the APR calculation for the pools, we use a separate backend solution called postgraphile due to some constraints in the TheGraph protocol we use as Backend. We will retire postgraphile, and the calculation will be served directly from our main backend (Subgraph).
Start consuming the monthly and weekly performance from our main graphQL API for the StakingPools
. Display it when the apr flag is disabled and newPerformanceEnabled is on.
newPerformanceEnabled
).apr
flag is on.newPerformanceEnabled
)apr
flag is disabled in the Performance pool table.apr
flag is disabled and newPerformanceEnabled
is on, I can see the performance numbers coming from Subgraph.Here are the staking pool's commissions page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
Commissions
space.
Setup the theme configuration to start using the Dark mode instead of the light mode.
Update the dependencies defined in the packages/utils
.
Package Current Wanted Latest Workspace Package Type URL
@types/react-dom 18.2.5 18.2.6 18.2.6 @explorer/utils devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom
@types/react 18.0.26 18.2.14 18.2.14 @explorer/utils devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react
eslint 7.32.0 7.32.0 8.44.0 @explorer/utils devDependencies https://eslint.org
typescript 4.9.4 4.9.5 5.1.6 @explorer/utils devDependencies https://www.typescriptlang.org/
Update the dependencies defined in the packages/ui
to avoid staying behind too much.
Note: Be mindful of major bumps
Package Current Wanted Latest Workspace Package Type URL
eth-chains 1.0.0 1.0.0 2.0.0 @explorer/ui dependencies
ethers 5.4.7 5.4.7 6.6.2 @explorer/ui dependencies https://ethers.org
humanize-duration 3.27.0 3.27.0 3.28.0 @explorer/ui dependencies https://github.com/EvanHahn/HumanizeDuration.js
react-icons 4.9.0 4.9.0 4.10.1 @explorer/ui dependencies https://github.com/react-icons/react-icons#readme
@storybook/addon-actions 6.5.15 6.5.16 7.0.24 @explorer/ui devDependencies https://github.com/storybookjs/storybook/tree/next/code/addons/actions
@storybook/addon-essentials 6.5.15 6.5.16 7.0.24 @explorer/ui devDependencies https://github.com/storybookjs/storybook/tree/next/code/addons/essentials
@storybook/addon-links 6.5.15 6.5.16 7.0.24 @explorer/ui devDependencies https://github.com/storybookjs/storybook/tree/next/code/addons/links
@storybook/react 6.5.15 6.5.16 7.0.24 @explorer/ui devDependencies https://github.com/storybookjs/storybook/tree/next/code/renderers/react
@testing-library/react 13.4.0 13.4.0 14.0.0 @explorer/ui devDependencies https://github.com/testing-library/react-testing-library#readme
@types/humanize-duration 3.25.1 3.25.1 3.27.1 @explorer/ui devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/humanize-duration
@types/react 18.0.26 18.2.14 18.2.14 @explorer/ui devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react
@types/react-dom 18.2.5 18.2.6 18.2.6 @explorer/ui devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom
eslint 7.32.0 7.32.0 8.44.0 @explorer/ui devDependencies https://eslint.org
jest 29.3.1 29.5.0 29.5.0 @explorer/ui devDependencies https://jestjs.io/
jest-canvas-mock 2.5.1 2.5.2 2.5.2 @explorer/ui devDependencies https://github.com/hustcc/jest-canvas-mock#readme
jest-environment-jsdom 29.3.1 29.5.0 29.5.0 @explorer/ui devDependencies https://github.com/facebook/jest#readme
jest-mock-extended 2.0.9 2.0.9 3.0.4 @explorer/ui devDependencies https://github.com/marchaos/jest-mock-extended
storybook-addon-apollo-client 4.1.4 4.1.4 5.0.0 @explorer/ui devDependencies https://github.com/lifeiscontent/storybook-addon-apollo-client#readme
storybook-addon-next-router 3.1.1 3.1.1 4.0.2 @explorer/ui devDependencies https://github.com/lifeiscontent/storybook-addon-next-router#readme
storybook-addon-performance 0.16.1 0.16.1 0.17.1 @explorer/ui devDependencies https://github.com/atlassian-labs/storybook-addon-performance#readme
typescript 4.9.4 4.9.5 5.1.6 @explorer/ui devDependencies https://www.typescriptlang.org/
Update the dependencies defined in the packages/wallet
.
PS: That does not include the onboarding dependencies because it is worked on issue #24
Package Current Wanted Latest Workspace Package Type URL
@unleash/proxy-client-react 3.3.0 3.3.0 3.6.0 @explorer/wallet dependencies https://github.com/Unleash/unleash-proxy-react#readme
@types/react-dom 18.2.5 18.2.6 18.2.6 @explorer/wallet devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom
@types/react 18.0.26 18.2.14 18.2.14 @explorer/wallet devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react
eslint 7.32.0 7.32.0 8.44.0 @explorer/wallet devDependencies https://eslint.org
jest 29.3.1 29.5.0 29.5.0 @explorer/wallet devDependencies https://jestjs.io/
jest-environment-jsdom 29.3.1 29.5.0 29.5.0 @explorer/wallet devDependencies https://github.com/facebook/jest#readme
jest-mock-extended 2.0.9 2.0.9 3.0.4 @explorer/wallet devDependencies https://github.com/marchaos/jest-mock-extended
typescript 4.9.4 4.9.5 5.1.6 @explorer/wallet devDependencies https://www.typescriptlang.org/
Jest
.eslint
.Here are the home page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references on colours, fonts and the overall look and feel of a page.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
A Home page example is already in the Figma file for Dark mode for easier reference.
Block
space. Keep the current grid system of 2 columns for big screens and 1 column for small ones for the Card.Block Producers
space.
staking
button colour in the stake/info
column.We noticed that unit tests take a lot of time to execute while not containing anything heavy in terms of computations.
Most of the time, those tests contain some mocks and simple checks that should be rather fast. Mocks are stored in memory and we are not calling any third-party services so the large amounts of time required for tests to execute are not justified. This also impacts our builds as they are slower than expected.
There are multiple things we can do to improve unit tests speed. An example is to optimize imports since jest (our test runner) takes more time to process large imports than specific ones.
Example from packages/ui
:
This is slower:
import { StakePlusIcon } from '../../src/components';
than this:
import { StakePlusIcon } from '../../src/components/Icons';
test:ci
command.--runInBand
flag for test:ci
. For reference - https://jestjs.io/docs/cli#--runinband.We noticed that unit tests take a lot of time to execute while not containing anything heavy in terms of computations.
Most of the time, those tests contain some mocks and simple checks that should be rather fast. Mocks are stored in memory and we are not calling any third-party services so the large amounts of time required for tests to execute are not justified. This also impacts our builds as they are slower than expected.
There are multiple things we can do to improve unit tests speed. An example is to optimize imports since jest (our test runner) takes more time to process large imports than specific ones.
Example from packages/ui
:
This is slower:
import { StakePlusIcon } from '../../src/components';
than this:
import { StakePlusIcon } from '../../src/components/Icons';
test:ci
command.--runInBand
flag for test:ci
. For reference - https://jestjs.io/docs/cli#--runinband.The current package in the explorer repository still exhibits redundancy in the wallet modules.
The package mentioned (apps/staking) has duplicate modules found in the packages/wallet directory:
package.json in apps/staking: link
package.json in packages/wallet: link
The objective of this issue is to eliminate the redundancy, ensuring that the wallet packages are only loaded from the packages/wallet directory.
apps/staking
packages/wallet
Duplicate content, move to #24
As we move to the public repository, all the integrations must be set again. Also, as we are moving to a trunk-based development, the Vercel configuration for deployment will change, and production will be based on tag publishing only and the main
and other branches for the preview environment.
Create new projects on Vercel for rollups and staking. Keep the main branch as the default, but add a new branch to be the production representation and keep using the branch-based deploy on Vercel.
main
branch will be the preview environment (Preview Domain associated)production
branch will be the one published on production environment. (Production domain associated)main
are deployed in preview mode and associated with the https://preview.explorer.cartesi.io
domain.Here are the stake page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
Summary
space. i.e. three cards with pool and stake information.My Staking Pools
space.
staking
icon colour in the stake/info
column.All Pools Performance
space.
staking
icon colour in the stake/info
column.Here are the stake page changes on colour, skin tones and fonts in Light Mode
to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #82
Summary
space. i.e. three cards with pool and stake information.My Staking Pools
space.
staking
icon colour in the stake/info
column.All Pools Performance
space.
staking
icon colour in the stake/info
column.Currently, we are using Storybook, and for every pull-request and push, we publish to Chromatic. Apparently, it works as expected since we use the storybook-build command and publish the folder with the static content. But if we use the yarn storybook
command inside the apps/staking folder, for example, or in the root of the project through turborepo task,
the build goes well (without any failures), the app opens, but all the stories display this Storybook preview hook
error message.
Recently we did some upgrades in the storybook libs/deps. An investigation would be necessary to see in which tag for example that problem may have been introduced, the tags may help to narrow down the changes since we have compares defined inside the CHANGELOG.md.
yarn storybook
command stops working properly.yarn storybook
renders the stories without problem.Add more unit tests in order to increase the test coverage for packages/wallet
workspace. Aim for 75%
coverage.
75%
Currently, the explorer rollups will need to support different cases, e.g. as a Web application maintained by us to consume all the DApps and provide a few pieces of information about each one of them, containerize to run locally to support the development and as a part of the deployment package for a single DApp when it is deployed somewhere. Hence, that differs from the usual web app; maintenance is gold here.
We have a few stable structures in place.
/
where we provide an overall number of DApps and inputs and a paged list of DApps./dapp/address-of-the-dapp
with more informational data when possible about the DApp.src/generated
folder.We want two things out of this issue.
src/generated/v0.8
and src/generated/v0.9
or something close to that with clear package/namespace separation. The rollups from v0.6.x to v0.8.x will benefit from the same queries and type definitions. The v0.9 has breaking changes; the Epoch
concept is gone from the graph tree, and now it is all about the Input.Container pattern
as discussed previously. It should use the rollups version of that DApp to decide which container to use.I am adding the tasklist in a specific order because the expected code generation structure will be used to inject in the containers. So, generation first and UI second.
Tasklist code generation:
dev
and build
comes from Turborepo i.e. from the root folder.Tasklist UI:
ps: Keep an eye on GitHub-actions and Vercel CI.
Available query to retrieve data about the factory version: dapps
| dapp
Network | Endpoint |
---|---|
https://api.thegraph.com/subgraphs/name/cartesi/rollups-goerli | |
https://api.thegraph.com/subgraphs/name/cartesi/rollups-arbitrum-goerli |
The new brand requires a new set of colours to support the overall looking and feel of the applications, i.e. Staking and Rollups.
PS: Refer to the parent issue for design references.
Include the new set of colours to support the system. As a suggestion, the reference colours are single instead of pallets, so I suggest being mindful and using the same language used by the design team, for example;
[Suggestion]: Adding to the theme's colours definition;
{
dark: {
support: {
success: #BDE08D,
alert: #FEB274,
error: #FF8D78
}
}
}
Later, we could refine and leverage the use of Chakra-ui Sematic Tokens
Here are the node-runners staking pool management page
changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
Pool Node
area when the node is hired:
RETIRE
button.Node balance
modal.Retire node
modal.Pool Node
area when the node is not hired:
Node history
area:
Pool Setting
area:
That is a one-off change in the navbar and footer that will benefit the work to be done on multiple pages.
*PS: Refer to the parent of this issue for references.
NavBar
space where the Logo, links and wallet button lies.Footer
space.The DApps details view currently shows a message for error when there are problems with the guessed URL, or it lists the inputs in case we have data. For the use case where the graphQL connection is established without problems, but there are no Inputs, we display an empty body below the search. It is not bad; however, we can do a bit a better ๐
Display a centralised message to provide feedback that all is well, but the DApp has not produced any inputs yet. The key points are;
Looks like there are no inputs yet...
Here are the node runners private node creation
page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
backlink
.page title
.learn from tutorial
link.Set up Ethereum node
step.Set up node
step.Hire node
step.Set allowance
step.StepGroup <Header>
.Here are the node runners staking pool creation
page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
backlink
.page title
.learn from tutorial
link.Set up Ethereum node
step.Set up node
step.Commission Model
step.Hire node
step.Pool ENS
step.StepGroup <Header>
. May have already been done on #67We made some house cleaning for old versions of rollups (i.e., rollups v0.8.2), but some definitions are still lingering around and another round of cleaning is necessary.
Remove and delete the graphQL schema definition for v0.8.
schema.graphql
for v0.8. located on graphql/schema/v0.8.
Add more unit tests in order to increase the test coverage for apps/staking
workspace. Aim for 75%
coverage.
75%
Here are the Blocks page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
Block Chart
as necessary. ps: Attention that the chart contains a list of colours to differentiate the list of entries for each different chainBlock list by all
cads.Block list by producers
cards.Block list by nodes
cards.In the rollups explorer, we list the latest N inputs that could contain notices, reports, and vouchers in the DApp details view. But a hard refresh would be needed to check for new Inputs that may have come through. Not bad, but a better experience could be added to fetch the latest data.
A switch should be added in the DApp details view to start the fetching process of the latest inputs. A few key points below;
Enable auto refresh?
followed by the switch.inputEdge
Rollups version v0.8.x helped the development team to build support for the local development of DApps. But since v0.9.0 is the target, we could remove everything related to v0.8.2.
Remove the dependency for rollups v0.8.2 and adapt the components that use it that support DApp local development.
InputFacet
and other hooks.The new brand uses a new set of fonts for different purposes. We need to add these new typefaces to our system to be used widely, meaning both Staking and Rollups applications.
PS: Refer to the parent of this issue for references.
Subgraph was the first (allegedly) good solution in the market as an indexing protocol. Still, it lacks flexibility on the graphQL API that force us to create summary entities here and there and more complex cases with pagination become constrained, if not impossible. Furthermore, we can't extend the graphQL API with custom resolvers which would be a killer feature (making that experiment unnecessary); on top of that is the language chosen, i.e. AssemblyScript, which is confusing since it uses the extension .ts
, causing all sorts of pitfalls along the way until you become a scarred warrior ๐ฅท. Besides that, the way we have our Subgraph set is working, but I want to look at other indexing protocol solutions available like subsquid or satsuma
For this experiment, I will pick the Subsquid. I'll add the pros and cons below and focus on my perceived benefits from the DX perspective. The deployment of the squid in the Aquarium service has its learning curve and details (e.g. Premium users vs Free users).
Here are the node runners
main page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
PS: A highlight for the two cases
below. observe the spacing and difference in colours in between blocks, meaning they are not glued.
Create a node or pool in steps
title.Create a public pool
card.
Run a private node
card.
Pool
block
create pool
buttonPrivate node
block
We will sunset subgraph support on our infrastructure, lowering costs and maintenance work. So we will be replacing the current AWS with another provider called Chainstack
Replace all AWS-related configurations with Chainstack's. That includes;
aws
and apr
(all related to AWS and the extended version provided by Postgraphile )in the code base.Here are the staking pool's user page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
Total Users
space
Staking users
space.
molecule tooltip
for the column Shares
.The new brand requires a new set of colours to support the overall looking and feel of the applications, i.e. Staking and Rollups.
PS: Refer to the parent issue for design references.
Include the new set of colours to support the system. As a suggestion, the reference colours are single instead of pallets, so I suggest being mindful and using the same language used by the design team, for example;
[Suggestion]: Adding to the theme's colours definition;
{
light: {
support: {
success: #7CA154
alert: #FFA77A,
error: #FD7267,
info: #B5E8F4
}
}
}
Later, we could refine and leverage the use of Chakra-ui Sematic Tokens
Cartesi has changed its brand; we must also upgrade our side and reflect on these new colours, fonts and overall look and feel. The Design team is working on batches, and the first is the changes in the skin and colour tones for Dark Mode and Light Mode
PS: This will be an epic issue, holding all the references to other spawn issues related to this work.
Upgrade the Chakra-ui theme and make any adjustments to the pages based on the guidelines in the Figma definition for Dark Mode and Light Mode.
Figma Reference: Explorer design system (new Dark mode)
Figma Reference: Explorer design system (new Light Mode)
Another ref: New component update, but mostly can be seen on Figma.
Fonts:
Vercel Deployment (New merges, updates the following): Application Preview
We need to update our copyright. Below is a more detailed context including some links.
Hey all, to more closely align with the reality that Cartesi is built by an ever-growing ecosystem of independent contributors -- and in order to bring recognition to the copyrighted contributions of individual authors -- the recommended course of action for copyright notices in all official Cartesi Github repositories is as follows:
- All existing copyright notices pertaining to code written by Cartesi contributors that is licensed under Apache 2.0 should be changed to:
(c) Cartesi and individual authors (see AUTHORS)
SPDX-License-Identifier: Apache-2.0 (see LICENSE)
- All existing copyright notices pertaining to code written by Cartesi contributors that is licensed under LGPL-3.0 should be changed to:
(c) Cartesi and individual authors (see AUTHORS)
SPDX-License-Identifier: LGPL-3.0 (see LICENSE)
No year is needed for any copyright notice.
Each repository should contain an AUTHORS file. Any contributor who has in the past had at least one pull request for a code change accepted in that repo may submit a pull request to have their name added to the AUTHORS file. Submissions to the AUTHORS file should be in the format:
Name <email>
In the first instance, the individual contributor(s) responsible for approving pull requests for that repo will need to manually check that the author submitting their name for inclusion previously had a pull request for a code change accepted in that repo. Contributors may then seek a way to automate this process moving forward.
Inclusion in the AUTHORS file for each repo is entirely voluntary. It is up to each individual author to decide whether they would like attribution in a given AUTHORS file and to submit a pull request accordingly. Please note that a contributor's decision on whether to seek attribution in an AUTHORS file will have no impact on copyright ownership.
See https://discord.com/channels/600597137524391947/1130905237901803560/1131962825695297567
Issue: cartesi/rollups#199
PR: cartesi/rollups#203
Subtask of this task. In this one, we should focus on updating ethers dependencies.
Here are the staking pool's stake page changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
Staking in a few steps
block. i.e. Icons, the text has the correct font and sizes applied to it.localStorage
to see it.TransactionBanner
blocks for.
Staking area
notification/warning
message.Your Pool Balance
card.Your staked balance
cardmy staking activities
area
Update dependencies defined in the root project to avoid staying behind. Just be mindful of the ones with major
bumps.
Package Current Wanted Latest Workspace Package Type URL
@chakra-ui/icons 2.0.10 2.0.10 2.0.19 explorer dependencies https://github.com/chakra-ui/chakra-ui#readme
@chakra-ui/react 2.3.4 2.3.4 2.7.1 explorer dependencies https://chakra-ui.com/
@chakra-ui/theme-tools 2.0.11 2.0.11 2.0.18 explorer dependencies https://github.com/chakra-ui/chakra-ui#readme
@unleash/proxy-client-react 3.3.0 3.3.0 3.6.0 explorer dependencies https://github.com/Unleash/unleash-proxy-react#readme
unleash-proxy-client 2.2.1 2.2.1 2.5.0 explorer dependencies https://github.com/unleash/unleash-proxy-client-js#readme
turbo 1.6.3 1.10.7 1.10.7 explorer devDependencies https://turbo.build/repo
prettier 2.8.2 2.8.8 2.8.8 explorer devDependencies https://prettier.io
framer-motion 4.1.17 4.1.17 10.12.18 explorer dependencies https://github.com/framer/motion#readme
Chakra-UI
.Unleash
.framer-motion
.prettier
version. If anySubtask of this task. In this one, we should focus on updating jest dependencies and fix any errors that may come up.
That is a one-off change in the navbar and footer that will benefit the work done on multiple pages.
*PS: Refer to the parent of this issue for references.
NavBar
space where the Logo, links and wallet button lies.Footer
space.Here are the home page changes on colour, skin tones and fonts in Light mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references on colours, fonts and the overall look and feel of a page.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #82
A Home page example is already in the Figma file for Light mode for good reference.
Block
space. Keep the current grid system of 2 columns for big screens and 1 column for small ones for the Card.Block Producers
space.
staking
button colour in the stake/info
column.Onboard is the library used to deal with wallet integration. We need to upgrade the core library and all the extra modules. Also, eliminate the duplication of dependency between the package/wallet and apps/staking since we move to a monorepo setup.
Package Current Wanted Latest Workspace Package Type URL
@web3-onboard/coinbase 2.2.0 2.2.0 2.2.4 staking dependencies https://onboard.blocknative.com
@web3-onboard/coinbase 2.2.0 2.2.0 2.2.4 @explorer/wallet dependencies https://onboard.blocknative.com
@web3-onboard/core 2.11.0 2.11.0 2.20.2 staking dependencies https://onboard.blocknative.com
@web3-onboard/core 2.11.0 2.11.0 2.20.2 @explorer/wallet dependencies https://onboard.blocknative.com
@web3-onboard/gnosis 2.1.5 2.1.5 2.1.10 staking dependencies https://onboard.blocknative.com
@web3-onboard/gnosis 2.1.5 2.1.5 2.1.10 @explorer/wallet dependencies https://onboard.blocknative.com
@web3-onboard/injected-wallets 2.4.0 2.4.0 2.10.1 staking dependencies https://onboard.blocknative.com
@web3-onboard/injected-wallets 2.4.0 2.4.0 2.10.1 @explorer/wallet dependencies https://onboard.blocknative.com
@web3-onboard/ledger 2.3.2 2.3.2 2.4.6 staking dependencies https://onboard.blocknative.com
@web3-onboard/ledger 2.3.2 2.3.2 2.4.6 @explorer/wallet dependencies https://onboard.blocknative.com
@web3-onboard/react 2.4.1 2.4.1 2.8.7 staking dependencies https://onboard.blocknative.com
@web3-onboard/react 2.4.1 2.4.1 2.8.7 @explorer/wallet dependencies https://onboard.blocknative.com
@web3-onboard/walletconnect 2.2.1 2.2.1 2.3.9 staking dependencies https://onboard.blocknative.com
@web3-onboard/walletconnect 2.2.1 2.2.1 2.3.9 @explorer/wallet dependencies https://onboard.blocknative.com
Currently, we are using the @cartesi/[email protected], but a new version (0.9.1) was released last month. Let's bump the performance to keep following the latest updates.
Mainnet, Goerli
Staking
The arrow on the Total Users should be inline with the text like the Total Rewards
The arrow is below the text
Check the UI on all display: mobile, tablet, desktop.
No response
We have been using QEMU to generate our rollups docker image. Previously it was only generating the images using the Linux/amd64 architecture, and the times were reasonable, around 6 minutes without intermittent connectivity problems. Once we included the Linux/arm64, though, the timing for that generation alone is around 26 minutes, and we often see network connectivity problems (screenshot below) naturally followed by CI failure because it usually never recovers that connection. Therefore, we are looking for an alternative to solve that problem and avoid the workaround, that is, to rerun it ๐ซ .
Initially, move from QEMU to depot.dev, which is specialised in building docker images. PS: funny enough, the example on the main page is showing how fast it is to build something on arm64
Reference: Sunodo CLI Action
DEPOT_PROJECT
for rollups-explorer on depot.dev.DEPOT_PROJECT
in the repository vars config to be available to the GitHub action.id-token: write
to be able to request JWT
token.depot.dev
rollups-explorer
images are published to the GitHub Registry a.k.a packages.Currently, when a tag it will also start an action to package a docker image for rollups to be published not just on the GitHub container registry but also on the docker hub. But we need the credentials set in the repository to publish the image. Also, change how we trigger the GA for rollups-explorer docker image generation.
PS: Added extra things in bold
Add the docker hub credentials to the repository settings to be available for our GitHub actions. Also, we will trigger the GitHub action for rollups packaging based on tag versioning.
[email protected]
, which results in a docker image tag like cartes/rollups-explorer:0.9.0explorer-rollups
could be published to the docker hub.Here are the staking pool page checkboxes for changes in colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
Summary
space. i.e. Staking pool cards e.g. Users / Commissions./ Staked balancePool Activity
space.
Subtask of this task. In this one, we should focus on updating storybook dependencies.
Here are the node-runners private node management page
changes on colour, skin tones and fonts in Dark mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PSยฒ: Don't worry about the header and footer, because that is addressed in a separate issue #62
CTSI
area:
Wallet Balance
block, including Tooltip.Allowance
block, including Tooltip and action button.Set Allowance
modal content, including its feedback UI.Pool Node
area when the node is hired:
RETIRE
& AUTHORIZE
.Node balance
modal.Retire node
modal.Pool Node
area when the node is not hired:
Node history
area:
Staking area
notification/warning
message.Unstake
& Stake
.Maturing
card, including any transitional state, e.g. Timers, etc.Your Staked Balance
card, including any transitional state, e.g. Timers, etc.Released
card. PS: To see the WITHDRAW
action link, you need unstacked CTSITransactionBanner
blocks (Redundancy check).
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.