Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@fuel-infrastructure/fuelsequencerjs
Advanced tools
FuelSequencerJS is a TypeScript library to interact with FuelSequencer
FuelSequencerJS is a TypeScript library to interact with FuelSequencer
npm install fuelsequencerjs
import { fuelsequencer } from 'fuelsequencerjs';
const { createRPCQueryClient } = fuelsequencer.ClientFactory;
const client = await createRPCQueryClient({ rpcEndpoint: RPC_ENDPOINT });
// now you can query the cosmos modules
const balance = await client.cosmos.bank.v1beta1
.allBalances({ address: 'fuelsequencer1addresshere' });
// you can also query the fuelsequencer modules
const balances = await client.fuelsequencer.exchange.v1beta1
.exchangeBalances()
Import the fuelsequencer
object from fuelsequencerjs
.
import { fuelsequencer } from 'fuelsequencerjs';
const {
createSpotLimitOrder,
createSpotMarketOrder,
deposit
} = fuelsequencer.exchange.v1beta1.MessageComposer.withTypeUrl;
import { cosmwasm } from "fuelsequencerjs";
const {
clearAdmin,
executeContract,
instantiateContract,
migrateContract,
storeCode,
updateAdmin
} = cosmwasm.wasm.v1.MessageComposer.withTypeUrl;
import { ibc } from 'fuelsequencerjs';
const {
transfer
} = ibc.applications.transfer.v1.MessageComposer.withTypeUrl
import { cosmos } from 'fuelsequencerjs';
const {
fundCommunityPool,
setWithdrawAddress,
withdrawDelegatorReward,
withdrawValidatorCommission
} = cosmos.distribution.v1beta1.MessageComposer.fromPartial;
const {
multiSend,
send
} = cosmos.bank.v1beta1.MessageComposer.fromPartial;
const {
beginRedelegate,
createValidator,
delegate,
editValidator,
undelegate
} = cosmos.staking.v1beta1.MessageComposer.fromPartial;
const {
deposit,
submitProposal,
vote,
voteWeighted
} = cosmos.gov.v1beta1.MessageComposer.fromPartial;
⚡️ For web interfaces, we recommend using cosmos-kit. Continue below to see how to manually construct signers and clients.
Here are the docs on creating signers in cosmos-kit that can be used with Keplr and other wallets.
Use getSigningfuelsequencerClient
to get your SigningStargateClient
, with the proto/amino messages full-loaded. No need to manually add amino types, just require and initialize the client:
import { getSigningfuelsequencerClient } from 'fuelsequencerjs';
const stargateClient = await getSigningfuelsequencerClient({
rpcEndpoint,
signer // OfflineSigner
});
To broadcast messages, you can create signers with a variety of options:
Likely you'll want to use the Amino, so unless you need proto, you should use this one:
import { getOfflineSignerAmino as getOfflineSigner } from 'cosmjs-utils';
import { getOfflineSignerProto as getOfflineSigner } from 'cosmjs-utils';
WARNING: NOT RECOMMENDED TO USE PLAIN-TEXT MNEMONICS. Please take care of your security and use best practices such as AES encryption and/or methods from 12factor applications.
import { chains } from 'chain-registry';
const mnemonic =
'unfold client turtle either pilot stock floor glow toward bullet car science';
const chain = chains.find(({ chain_name }) => chain_name === 'fuelsequencer');
const signer = await getOfflineSigner({
mnemonic,
chain
});
Now that you have your stargateClient
, you can broadcast messages:
const { send } = cosmos.bank.v1beta1.MessageComposer.withTypeUrl;
const msg = send({
amount: [
{
denom: 'coin',
amount: '1000'
}
],
toAddress: address,
fromAddress: address
});
const fee: StdFee = {
amount: [
{
denom: 'coin',
amount: '864'
}
],
gas: '86364'
};
const response = await stargateClient.signAndBroadcast(address, [msg], fee);
If you want to manually construct a stargate client
import { OfflineSigner, GeneratedType, Registry } from "@cosmjs/proto-signing";
import { AminoTypes, SigningStargateClient } from "@cosmjs/stargate";
import {
cosmosAminoConverters,
cosmosProtoRegistry,
cosmwasmAminoConverters,
cosmwasmProtoRegistry,
ibcProtoRegistry,
ibcAminoConverters,
fuelsequencerAminoConverters,
fuelsequencerProtoRegistry
} from 'fuelsequencerjs';
const signer: OfflineSigner = /* create your signer (see above) */
const rpcEndpint = 'https://rpc.cosmos.directory/fuelsequencer'; // or another URL
const protoRegistry: ReadonlyArray<[string, GeneratedType]> = [
...cosmosProtoRegistry,
...cosmwasmProtoRegistry,
...ibcProtoRegistry,
...fuelsequencerProtoRegistry
];
const aminoConverters = {
...cosmosAminoConverters,
...cosmwasmAminoConverters,
...ibcAminoConverters,
...fuelsequencerAminoConverters
};
const registry = new Registry(protoRegistry);
const aminoTypes = new AminoTypes(aminoConverters);
const stargateClient = await SigningStargateClient.connectWithSigner(rpcEndpoint, signer, {
registry,
aminoTypes
});
When first cloning the repo:
yarn
yarn build
Contract schemas live in ./contracts
, and protos in ./proto
. Prior to codegen, the protos can be updated as follows:
telescope download --config scripts/.protod.config.json
You will need to have access to any private repository listed in the
scripts/.protod.config.json
file.Make sure that you're getting protos from the expected versions by checking the "branch" fields in the
.protod.config.json
file.As a backup, the protos can also be updated manually, by checking out the respective repositories and copying over the proto files.
Look inside of scripts/codegen.js
and configure the settings for bundling your SDK and contracts into fuelsequencerjs
:
yarn codegen
Before committing any changes to src/codegen/
, check if it builds successfully:
yarn build
Build the types and then publish:
yarn build
yarn publish --access public
# or npm publish --access public
Checkout these related projects:
🛠 Built by Cosmology — if you like our tools, please consider delegating to our validator ⚛️
AS DESCRIBED IN THE LICENSES, THE SOFTWARE IS PROVIDED “AS IS”, AT YOUR OWN RISK, AND WITHOUT WARRANTIES OF ANY KIND.
No developer or entity involved in creating this software will be liable for any claims or damages whatsoever associated with your use, inability to use, or your interaction with other users of the code, including any direct, indirect, incidental, special, exemplary, punitive or consequential damages, or loss of profits, cryptocurrencies, tokens, or anything else of value.
FAQs
FuelSequencerJS is a TypeScript library to interact with FuelSequencer
The npm package @fuel-infrastructure/fuelsequencerjs receives a total of 25 weekly downloads. As such, @fuel-infrastructure/fuelsequencerjs popularity was classified as not popular.
We found that @fuel-infrastructure/fuelsequencerjs demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.