Skip to content

Add Blux to the Stellar skills catalog - #144

Merged
kaankacar merged 4 commits into
stellar:mainfrom
ceydae:main
Oct 7, 2026
Merged

kaankacar merged 4 commits into
stellar:mainfrom
ceydae:main

Conversation

@ceydae

@ceydae ceydae commented Oct 1, 2026

Copy link
Copy Markdown
Contributor
  • Added Blux to the skills catalog so developers can add it to their Stellar projects.
  • Added examples showing how to use Blux for login, payments, transactions, balances, and Soroban contract reads.
  • Updated the dApp evaluation to recognize Blux as an option.

@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

Thanks for this, Ceyda. The hook examples are clear and short. I checked them against the published @bluxcc/react and @bluxcc/core 0.3.9 types: useBlux, useTransfer, useReadContracts and core.getBalances all match. Every link resolves.

You are the main contributor to bluxcc/core. So this PR adds your own project to the official dapp skill. That listing decision belongs to a maintainer. @kaankacar will decide it. I will not merge it before then.

You can fix these items now:

  1. Provider Component (react.md). The PR replaces the neutral Providers example with a Blux-only one. Every reader would then need Blux and an appId. Please keep the original and add Blux as a separate, optional snippet.
  2. Default network. The dapp skill examples default to testnet. Blux runs on Mainnet when networks is not set (your own Networks docs say so). Please add networks: [networks.testnet] to the provider snippet, so a copied useTransfer example does not send real XLM.
  3. Merge conflict. site/src/data/skills.ts conflicts with main. Please rebase onto current main.
  4. Card target. In docs.blux.cc/SKILLS.md, the TOKEN contract id has 55 characters. A valid contract id has 56. It appears twice.

@ceydae

ceydae commented Oct 7, 2026

Copy link
Copy Markdown
Contributor Author

The issues mentioned by Stellar Triage Bot have been fixed.

@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

Thanks, Ceyda. Your new commits fix two items well. The neutral Providers example is back. The Blux provider now sets networks: [networks.testnet]. I checked that networks.testnet is a real export in @bluxcc/react 0.3.9.

Your merge of main joined the Blux card and the Stellar Registry card into one object in skills.ts. That has duplicate keys, so the type check fails and one card is lost. I pushed a small fix (0cdba77): the Blux card is now its own entry, last in ECOSYSTEM_CARDS. The branch now merges cleanly with main.

One item is still open:

  • Card target. In docs.blux.cc/SKILLS.md (lines 195 and 256), the TOKEN contract id still has 55 characters. A valid contract id has 56. Please fix it on your docs site.

The listing decision is still with @kaankacar. I will not merge before he decides.

@ceydae

ceydae commented Oct 7, 2026

Copy link
Copy Markdown
Contributor Author

The docs is fixed now

@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

Thanks, Ceyda. The docs fix is good. Both TOKEN ids in docs.blux.cc/SKILLS.md now have 56 characters. The id is the live native XLM contract on Mainnet, which matches the Blux default network.

All four items from my first review are now resolved. The branch still merges cleanly with main.

Two things remain, and neither needs work from you:

  • The listing decision is with @kaankacar. I will not merge before he decides.
  • The site-ci build check is waiting for a maintainer to approve the run. The bot cannot approve it.

@kaankacar

Copy link
Copy Markdown
Contributor

yeah just merge it

@kaankacar
kaankacar merged commit bc76faf into stellar:main Oct 7, 2026
2 checks passed
@ceydae

ceydae commented Oct 8, 2026

Copy link
Copy Markdown
Contributor Author

Thank you @kaankacar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants