Merge branch 'develop' of https://github.com/klever-io/kos-rs into se…

…rialize-tx-into-raw-hex-trx

.coderabbit.yaml

@@ -0,0 +1 @@
+language: "en-US"

.github/workflows/stale.yaml

@@ -9,11 +9,10 @@ jobs:
   stale:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/stale@v8
+    - uses: actions/stale@v9
       with:
         repo-token: "${{ secrets.GITHUB_TOKEN }}"
         stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.'
         days-before-stale: 60
         days-before-close: 7
         stale-pr-message: 'This PR has been marked as stale due to lack of activity. It will be closed if no further activity occurs. Please check it out!'
-        stale-label: 'stale'

README.md

@@ -59,65 +59,3 @@ kos-rs = "0.1"
 - `packages/kos-utils/`: Package with utility libraries for various purposes.
 
 ---
-
-# Klever Bounty Program (kos-rs)
-
-Klever is on a quest for adept Rust developers to revamp its Rust-powered crypto wallet SDK, initially designed for WebAssembly (Wasm). The aim is to expand its compatibility for Kotlin (Android) and Swift (iOS) platforms. The ultimate objective is to streamline this transition, minimizing the manual coding interventions.
-
-## Rewards Distribution
-
-Bounty winners will be compensated with $KFI tokens. Here's the reward distribution:
-
-- [x] Web Wasm: 10,000 KFI 
-- [x] React Native Wasm): 10,000 KFI
-- [ ] Kotlin Rust SDK binding: 10,000 KFI (First PR Approved only)
-- [ ] Swift Rust SDK binding: 10,000 KFI (First PR Approved only)
-- [ ] Code Review PR Approval: 100 KFI
-
-## Key Milestones
-
-### 1. SDK Examination
-
-- Perform an in-depth review of the present SDK, focusing on its architecture, features, and Wasm-specific dependencies.
-
-### 2. Integration & Accessibility
-
-- Create essential bindings and exports to make Rust functions and types accessible from Wasm, Kotlin, and Swift.
-
-### 3. Security Assurance
-
-- Probe the existing and newly-developed code for potential threats and make necessary patches.
-
-### 4. Automation Implementation
-
-- Conceptualize and establish an automatic adaptation system, preferably using Rust's attributes/macros. This should ensure the central Rust code remains universally applicable.
-
-### 5. Validation
-
-- Rigorously test the SDK for Kotlin and Swift platforms, ensuring uniformity.
-- Integrate critical unit tests to validate performance.
-
-### 6. Documentation & Guidance
-
-- Deliver a detailed summary of the alterations and explain the workings of the automation tool.
-- Detail the integration process for Kotlin and Swift projects.
-
-### 7. Evidence of Testing
-
-- Produce provable test results for Kotlin and Swift platforms, including unit, integration, and other relevant test artifacts.
-
-## Evaluation Criteria
-
-- Effortless SDK integration with Kotlin and Swift.
-- Uniform SDK operations across Wasm, Kotlin, and Swift.
-- Significant minimization of manual code changes due to the automation tool.
-- Transparent and coherent documentation aiding seamless SDK integration for new developers.
-
-## Recommendations
-
-- To genuinely grasp the SDK's intricacies, having access or a sample of the existing Rust SDK is crucial. This aids in a well-informed transition.
-- The program should prioritize developers familiar with Rust FFI and Kotlin/Swift compatibility. This focus promises higher-quality, viable solutions.
-
-### Final Words
-
-We're eager to witness the pioneering solutions our community will present. Accomplishing this bounty's objectives will immensely boost our SDK's adaptability and appeal, enriching both developers and end-users.