four issues resolved: multi-currency contracts (37 tests passing), de… - #153

🌐 Web query:

For soroban_sdk token clients, what is the recommended way to validate a token/SAC contract address without trapping, and does token::StellarAssetClientexposetry_decimals() (or equivalent fallible APIs)?

💡 Result:

Recommended validation approach (no trapping): don’t call the infallible metadata methods (e.g., decimals()), because they are specified to panic if the SAC/token contract “has not yet been initialized” [1]. Instead, for Soroban token/SAC clients, prefer the fallible API that returns a Result (or otherwise gate your call behind a pre-check), so you can handle “not initialized / wrong contract” as an error rather than allowing a trap. For token::StellarAssetClient: yes—StellarAssetClient exposes a fallible equivalent of decimals() named try_decimals(&self) -> Result<..., Error> [2]. The docs also explicitly say decimals() panics when the contract hasn’t been initialized [2]. Caveat/contract-shape expectation: decimals(env) -> u32 is part of the StellarAssetInterface (CAP-46-6 functions) and is defined as panicking in that interface if the contract is not initialized [1][3]. So try_decimals() is the API you want when you need “validate that this address is a suitable SAC/token without trapping.”

Citations:

• 1: https://docs.rs/soroban-sdk/latest/src/soroban_sdk/token.rs.html
• 2: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
• 3: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/trait.StellarAssetInterface.html

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/bash
# Verify downstream PromptCreated handling is multi-asset aware
fd -i 'indexer.ts'
rg -n -C3 'PromptCreated|price_stroops|asset|10_000_000|10_000_0000' server/src/services/indexer.ts

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 954

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# 1) Inspect the PromptCreated event definition (asset field presence/types)
rg -n "PromptCreated" contracts/prompt-hash/src/events.rs
rg -n "asset" contracts/prompt-hash/src/events.rs
# Print the relevant sections around the matches (keep output small)
rg -n "PromptCreated" -n -C3 contracts/prompt-hash/src/events.rs
rg -n "asset" -n -C3 contracts/prompt-hash/src/events.rs

# 2) Inspect PromptCreated handling/normalization in the indexer
sed -n '1,160p' server/src/services/indexer.ts

# 3) Check whether asset/decimals is used anywhere near PromptCreated or price_stroops normalization
rg -n "price_stroops" server/src/services/indexer.ts
rg -n "asset" server/src/services/indexer.ts
rg -n "10_000_000" server/src/services/indexer.ts

# 4) Broader search: any other consumer of PromptCreated / price_stroops / asset decimals
rg -n "PromptCreated" server/src | head -n 50
rg -n "price_stroops" server/src | head -n 50
rg -n "\"PromptPriceUpdated\"" server/src | head -n 50
rg -n "10_000_000" server/src | head -n 50

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 4648

🏁 Script executed:

#!/bin/bash
set -euo pipefail
rg -n "struct PromptPriceUpdated|PromptPriceUpdated" contracts/prompt-hash/src/events.rs
rg -n "PromptPriceUpdated" -n -C3 contracts/prompt-hash/src/events.rs

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 488

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Locate PromptCreated emission
rg -n "emit_prompt_created|PromptCreated \{" contracts/prompt-hash/src -S
rg -n "price_stroops|asset" contracts/prompt-hash/src -S

# Show surrounding code for the emission (limit output)
rg -n "emit_prompt_created" -n -C5 contracts/prompt-hash/src

# If emit functions exist, inspect their definitions and any helpers that compute price
rg -n "fn emit_.*prompt.*" contracts/prompt-hash/src -S

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 10010

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect contract.rs around pricing/emit_prompt_created and decimals validation
sed -n '1,220p' contracts/prompt-hash/src/contract.rs

# Inspect server Prompt model to see if it stores asset/decimals
fd -i "*Prompt*" server/src -a
fd -i "prompt" server/src/models -a 2>/dev/null || true
ls -R server/src/models 2>/dev/null || true
rg -n "class Prompt|interface Prompt|mongoose.*Prompt|price|asset|decimals" server/src/models -S || true

# Inspect any DB update for asset during PromptCreated indexing
rg -n "asset" server/src/services/indexer.ts
rg -n "Prompt.findOneAndUpdate\\(" server/src/services/indexer.ts -n

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 7772

🏁 Script executed:

#!/bin/bash
set -euo pipefail
rg -n "10_000_000" server/src
rg -n "asset" server/src/models server/src/services/indexer.ts
fd -i "Prompt*" server/src/models -t f || true

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 265

🏁 Script executed:

#!/bin/bash
set -euo pipefail
rg -n "10_000_000" server/src
fd -i "Prompt*" server/src/models -t f || true
rg -n "class Prompt|interface Prompt|mongoose.*Prompt|asset|decimals" server/src/models server/src -S
rg -n "price_stroops" server/src -S

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 1251

🏁 Script executed:

#!/bin/bash
set -euo pipefail
sed -n '1,220p' server/src/models/Prompt.js
sed -n '1,120p' server/src/models/PromptVersion.ts
rg -n "asset|decimals|price_stroops|10_000_000" server/src/models/Prompt.js server/src/models/PromptVersion.ts server/src -S

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 2375

Since this is a numbered list rather than code, consider either:

Option 1 - Add a language identifier (e.g., text):

-```
+```text
 1. Validate listing (active, not duplicate, supply check)

Option 2 - Use markdown list formatting instead of a code block for better semantic markup.

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/bash
# Description: Check for ownership implementation in the contract

# Search for ownership-related macros or implementations
rg -n "only_owner|Ownable|OpenZeppelin" contracts/prompt-hash/

# Search for admin/owner authorization patterns
rg -nC3 "set_fee_percentage|set_pause_status" contracts/prompt-hash/src/contract.rs

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 2013

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show the relevant section of the docs with line numbers
sed -n '50,90p' docs/case-study-stellar.md | nl -ba -w2 -s': '

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 119

🏁 Script executed:

sed -n '50,90p' docs/case-study-stellar.md | nl -ba -w2 -s': '

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 119

🏁 Script executed:

#!/bin/bash
set -euo pipefail
sed -n '55,88p' docs/case-study-stellar.md | nl -ba -w2 -s': '

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 119

🏁 Script executed:

#!/bin/bash
set -euo pipefail

file="docs/case-study-stellar.md"

echo "== Matching docs references =="
rg -n "set_fee_percentage|only_owner|OpenZeppelin|Ownable" "$file" || true

echo
echo "== Docs lines 55-88 with line numbers (no nl) =="
sed -n '55,88p' "$file" | awk '{printf "%4d: %s\n", NR+54, $0}'

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 2065

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/bash
# Verify whether manual-chunked packages are imported via subpaths.
# Expected: If subpath imports exist, prefer function-based manualChunks.
rg -nP --type=ts --type=tsx --type=js --type=jsx -C2 \
'from\s+["'\''](`@stellar/stellar-sdk/`[^"'\'']+|`@stellar/stellar-base/`[^"'\'']+|chart\.js/[^"'\'']+|framer-motion/[^"'\'']+|libsodium-wrappers/[^"'\'']+)["'\'']'

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 104

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show relevant part of vite.config.ts
if [ -f "vite.config.ts" ]; then
  echo "=== vite.config.ts (manualChunks area) ==="
  nl -ba vite.config.ts | sed -n '1,120p'
  echo
fi

# Find subpath imports/usages for the packages in question
echo "=== occurrences of `@stellar/stellar-sdk/` (subpaths) ==="
rg -n --hidden --no-ignore -S "`@stellar/stellar-sdk/`" . || true

echo
echo "=== occurrences of `@stellar/stellar-base/` (subpaths) ==="
rg -n --hidden --no-ignore -S "`@stellar/stellar-base/`" . || true

echo
echo "=== occurrences of chart.js/ (subpaths) ==="
rg -n --hidden --no-ignore -S "chart.js/" . || true

echo
echo "=== occurrences of framer-motion/ (subpaths) ==="
rg -n --hidden --no-ignore -S "framer-motion/" . || true

echo
echo "=== occurrences of libsodium-wrappers/ (subpaths) ==="
rg -n --hidden --no-ignore -S "libsodium-wrappers/" . || true

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 180

🌐 Web query:

Rollup output.manualChunks object array of ids matching subpath module ids (e.g., manualChunks: {vendor: ['@stellar/stellar-sdk']} match '@stellar/stellar-sdk/rpc')

💡 Result:

In Rollup, the output.manualChunks option accepts either an object or a function to define custom shared chunks [1]. When you need to match specific subpath imports—such as @stellar/stellar-sdk/rpc—the function form is the required approach, as the object form only accepts exact module names or package identifiers to group those modules and their dependencies [1]. To target subpaths, you should implement a function that inspects the module ID passed to it. Example implementation: // rollup.config.js export default { //... output: { manualChunks(id) { // Check if the module ID contains the subpath if (id.includes('@stellar/stellar-sdk/rpc')) { return 'stellar-rpc'; // Name of the resulting chunk } // Fallback: handle other dependencies if (id.includes('node_modules')) { return 'vendor'; } } } }; Key considerations: 1. Object Form Limitation: The object form, such as manualChunks: { vendor: ['@stellar/stellar-sdk'] }, maps specific listed modules to a chunk [1]. It does not inherently provide pattern matching for subpath modules (e.g., it will not automatically include @stellar/stellar-sdk/rpc just because the parent package is listed) [1]. 2. Function Form Flexibility: The function form receives the resolved module ID as the first argument [1]. This allows you to use string methods like .includes(), .endsWith(), or regular expressions to match specific subpaths dynamically [1][2]. 3. Dependency Handling: When you return a string from the function, Rollup assigns that label to the module and all its dependencies, provided those dependencies have not already been assigned to a different manual chunk [1][3]. 4. Advanced Control: The function receives a second argument containing utility functions like getModuleInfo, which can be used for more complex logic if you need to inspect the dependency graph to determine if a module should be grouped [1][2].

Citations:

• 1: https://rollupjs.org/configuration-options/
• 2: Extend manualChunks API rollup/rollup#3542
• 3: Manual chunks function rollup/rollup#2831

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show relevant part of vite.config.ts
if [ -f "vite.config.ts" ]; then
  echo "=== vite.config.ts (manualChunks area) ==="
  nl -ba vite.config.ts | sed -n '1,120p'
  echo
fi

# Find subpath imports/usages for the packages in question
echo "=== occurrences of `@stellar/stellar-sdk/` (subpaths) ==="
rg -n --hidden --no-ignore -S "`@stellar/stellar-sdk/`" . || true

echo
echo "=== occurrences of `@stellar/stellar-base/` (subpaths) ==="
rg -n --hidden --no-ignore -S "`@stellar/stellar-base/`" . || true

echo
echo "=== occurrences of chart.js/ (subpaths) ==="
rg -n --hidden --no-ignore -S "chart.js/" . || true

echo
echo "=== occurrences of framer-motion/ (subpaths) ==="
rg -n --hidden --no-ignore -S "framer-motion/" . || true

echo
echo "=== occurrences of libsodium-wrappers/ (subpaths) ==="
rg -n --hidden --no-ignore -S "libsodium-wrappers/" . || true

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 180

🌐 Web query:

Rollup output.manualChunks object array of ids matching subpath module ids (e.g., manualChunks: {vendor: ['@stellar/stellar-sdk']} match '@stellar/stellar-sdk/rpc')

💡 Result:

To match subpath module IDs in Rollup's manualChunks, you must use the function form of the manualChunks configuration option [1][2]. The object form only allows static, exact mapping of modules to chunks, and does not support pattern matching or subpath logic [1]. When you use the function form, Rollup passes the module ID of every resolved file to your function [1]. You can then perform string matching or regex operations on that ID to return the desired chunk name [1][2]. Implementation approach: In your rollup.config.js (or vite.config.js): export default { //... output: { manualChunks(id) { // Check if the module belongs to the specific package or path if (id.includes('@stellar/stellar-sdk')) { return 'stellar-vendor'; // All files matching this path go into this chunk } // Default behavior for other modules if (id.includes('node_modules')) { return 'vendor'; } } } }; Key considerations: 1. Object Form Limitation: The object form, e.g., manualChunks: { vendor: ['@stellar/stellar-sdk'] }, only bundles the specific modules listed [1]. It does not automatically capture subpaths (e.g., @stellar/stellar-sdk/rpc) unless they are explicitly included in the array or handled by a plugin that resolves them [1]. 2. Function Form Flexibility: The function form is the authoritative way to handle complex grouping [1]. Because it receives the resolved ID, you can easily target specific subpaths by checking if the string starts with or includes your target path [2]. 3. Dependency Inclusion: When you return a chunk name for a module ID, Rollup automatically includes that module and all its dependencies in the specified chunk, unless those dependencies are already assigned to a different manual chunk [3][1][4]. 4. Evaluation Order: The function is evaluated for each module [1][4]. You can implement logic to prioritize certain chunks over others if a module belongs to multiple potential groups [3][5][4].

Citations:

• 1: https://rollupjs.org/configuration-options/
• 2: https://soledadpenades.com/posts/2025/use-manual-chunks-with-vite-to-facilitate-dependency-caching/
• 3: Manual chunks support rollup/rollup#2084
• 4: Manual chunks function rollup/rollup#2831
• 5: Allow more programmatic control over manual chunks rollup/rollup#2688

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# 1) Inspect vite.config.ts manualChunks
echo "=== vite.config.ts: manualChunks definition ==="
if [ -f "vite.config.ts" ]; then
  rg -n "manualChunks" vite.config.ts || true
  echo
  echo "=== vite.config.ts: lines 1-160 (manualChunks context) ==="
  # Avoid nl (not available). Use cat -n.
  cat -n vite.config.ts | sed -n '1,160p'
else
  echo "vite.config.ts not found"
fi

# 2) Search for subpath imports in the repo
patterns=(
  '`@stellar/stellar-sdk/`'
  '`@stellar/stellar-sdk/rpc`'
  '`@stellar/stellar-base/`'
  'chart.js/'
  'framer-motion/'
  'libsodium-wrappers/'
)

for p in "${patterns[@]}"; do
  echo
  echo "=== occurrences of pattern: $p ==="
  rg -n --hidden --no-ignore -S "$p" . || true
done

Repository: Obiajulu-gif/Prompt-Hash-Stellar

Length of output: 4547

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.