The issue-fee should be an sdk.Coin string, example: --issue-fee 1ubtsg and not --issue-fee 1

Command:
bitsongd tx fantoken issue --name Angelo --symbol angelo --max-supply 1000 --issue-fee 1000000 --from validator --chain-id test -b block

I have made a bond and chose the specified time and after the bond time ended I did an unbond and I want to remove liquidity I couldn't, all those who use the mobile web especially have the same problem sir

bitsong1j7v4yn6eewcfm07ze8ww6yn97r5y2nc5yghrwn

#114

If i want to transfer more than 1000 Token on more, the token didn't wan't to be transfered, i try more than 2 times but still same
So i have to transfer less than 1000 and it's goin fine

If I try the command bitsongd tx fantoken update there is confusion over descriptions

Usage:
bitsongd tx fantoken update [symbol] [flags]

Examples:
bitsongd tx token edit <symbol> --mintable=true --from=<key-name> --chain-id=<chain-id> --fees=<fee>

Solution:
change update to edit

In the bigbang-test-2 chain:

If I issue a token w/ an already taken name, it gives me an "Denom Already Exists" error. I created this token:

(Tx Hash: F1EADFF4B01E1A563EF7C58CCE669C0869C95926A44E9DC242D9990A868BC938)

bitsongd tx fantoken issue --issue-fee=1000000ubtsg --max-supply=1000000 --symbol="bug" --description="" --from=hathor --chain-id=bigbang-test-2 --fees=200ubtsg --name="BugToken"

If I check, I can tell I own this token now:

bitsongd query fantoken owner bitsong1uh0ncteup7tles2t6v32cc4adrfjhjzk2jnxpu

• max_supply: "1000000"
  meta_data:
  base: ft518F03EDBB4A1E66A694B6833A2235067692E8C0
  denom_units:
  • denom: ft518F03EDBB4A1E66A694B6833A2235067692E8C0
  • denom: bug
    exponent: 6
    display: bug
    mintable: true
    name: BugToken
    owner: bitsong1uh0ncteup7tles2t6v32cc4adrfjhjzk2jnxpu

If I try to recreate that same token:

bitsongd tx fantoken issue --issue-fee=1000000ubtsg --max-supply=1000000 --symbol="bug" --description="" --from=hathor --chain-id=bigbang-test-2 --fees=200ubtsg --name="BugToken"

bitsongd query tx --type=hash 0C63C51BB7FE63B6E1BEFC19BD7B52860C57A07E83ADAD799A0FFB6C926B89F1

I get the error: failed to execute message; message index: 0: denom already exists: ft518F03EDBB4A1E66A694B6833A2235067692E8C0

That denom matches my BugToken that I just made. If I rename my token to BuToken,

bitsongd tx fantoken issue --issue-fee=1000000ubtsg --max-supply=1000000 --symbol="bug" --description="" --from=hathor --chain-id=bigbang-test-2 --fees=200ubtsg --name="BuToken"

It works w/ a tx hash of BBEF623C4E6A0217C09B77EA4DCF4C16C1651FD301393F152036F5594417E447

I can check my ownership of both tokens:

bitsongd query fantoken owner bitsong1uh0ncteup7tles2t6v32cc4adrfjhjzk2jnxpu

If I transfer the token to someone else, I still can't make a token w/ a new name.

I can go into the testnet guide and make an Angelo's token even though other people have made that same token. But I can't reuse the same name twice myself.

I have done swap 2 transaction .. but next swap transaction still error .. i have 2200 BTSG but cannot swap .

when I first tried the swap feature, there was a slight bug, namely the swap failed, and to solve that problem every time I wanted to swap or make a transaction I refreshed the web page,,, and everything was normal and smooth, thank you
this is my address
bitsong1wqm3h0sc9zujeq4zn7ewhsvy6tgj3mcsgud5yv

I can't do swap when the step size is too big (170.444444444444 etc).
it doesn't even pop up a "transaction failed" message
my bitsong wallet bitsong1w60q3k507d9phcs7qqezt88w3ux5pzrlajhyd2

I have done ,swap ,add lp , remove lp ,and bond lp , and I didn't find any bugs and the web is running smoothly

Description

• When i sucsses deposit/make transaction my asset wallet POP UP cant close automatic, must be close manual is that very uncomfortable
• if i not close manual i cant make next transaction

Screenshot

Suggestion

• Maybe check your code betwen popup wallet and your web , this problem I didn't find it on any other web (on the same network)

My bitsong balance is showing 0 BTSG under Swap but shows 10,000 BTSG under Assets. I think this is a bug that need to be fix.

Wallet address: bitsong15nf8v5aj7t86avkcdtz9djlydevmzcsdr0wpyq

I tried to mint some fantoken, when we mint a new fantoken it will add 6 standard decimal and the result could be out of the proposed intentions.

Command

bitsongd tx fantoken mint clay --recipient bitsong1lemmdcgn087pd380p54q0f45pe7vrylcetu529 --amount 1000 --from validator --chain-id test

What I expect

I expect that with this command I will mint 1000 clay. Currently the chain mint 1000000000uclay

I think the best approach is to change the command to accept something like that

..... fantoken mint uclay --amount 1000000000

with that expression the account is sure to get the specified amount.

https://github.com/bitsongofficial/go-bitsong/blob/module/fantoken/x/fantoken/keeper/keeper.go#L166

This is the last BitSong Track Metadata implementation

To all Music Providers, we need feedbacks for this issue
If you consider that the structure has to be changed or improved, feel free to comment on the issue

{
  "title": "The show must go on",
  "artists": ["Artist 1", "Artist 2", "Artist 3"],
  "feat": ["Singer 1"],
  "producers": ["Producer 1"],
  "images": [
    { "32x32": "ipfs://Qm........"},
    { "500x500": "ipfs://Qm........"}
  ],
  "sources": [
    { "preview": "ipfs://Qm...." },
    { "hls": "ipfs://Qm...." },
    { "opus": "ipfs://Qm...." },
    { "mp3_low": "ipfs://Qm...." },
    { "mp3_high": "ipfs://Qm...." }
  ],
  "duration": 15001,
  "number": 1,
  "tags": ["tag 1", "tag 2", "tag 3"],
  "genre": "Pop",
  "mood": "Energetic",
  "label": "My best label",
  "credits": "Creative Commons",
  "external_ids": [
    { "youtube": "M7Iwkxy_Hjw" },
    { "spotify": "12487825" }
  ],
  "external_urls": [
    { "youtube": "https://www.youtube.com/watch?v=y6veLh2b1Js" },
    { "soudcloud": "https://soundcloud.com/bangtan/thankyouarmy2020" }
  ]
}

I tried to swap any pair on other token like ' adam clay ' and then enter the slippage from 1 till 7 but didn't work, then i tried on 10 its working
Maybe need some repairs at slippage moment, its very difficult if we need to change slippage and then try to find some slippage if wanna make a success swap

Hello.

We would like to get notifications of upcoming releases.

It would be a massive help if we could do it through Github's Slack integration.

Could you kindly install it?

Thank you

• Remove fantoken module
• Update to sdk-0.45.x
• Refactor appparams
• Add PrepareGenesisCmd
• Add/Fix TestnetCmd
• Fix simApp
• Fix simApp/staking
• Test sim
• Fix sim Makefile
• Test minCommission
• Move UpgradeHanlder
• Test exported state
• Test/Fix docker

If I try to transfer the ownership of a fantoken I get the following issue

Command:
bitsongd tx fantoken transfer angelo --to $(bitsongd keys show validator2 -a)

Error:
unknown flag: --to

Move modules from bitsongofficial/chainmodules to bitsongofficial/go-bitsong

• Fantoken module

I think i found a bug and perhaps it can make a confused for the user. As seen in the picture, in estimated slippage there is no big impact after i changed slippage tolerance from 1% to 5%. Thank you

My address: bitsong1nqyn8g22e8wpjjhll33j2tj36yn7n08yd9e6cz

Hi there,
this is the official scoreboard of bitsong-testnet-3 contest, prizes, bonuses and methods will be communicated as soon as possible.

Thanks for being part of bitsong-testnet-3

We need to allow FanToken symbols also starting with numbers.
We have to adapt this particular regex:

Ex:
^[a-z][a-z0-9]{%d,%d}$

Should be:

^[a-z0-9]{%d,%d}$

I had this error. bitsong19uts2g8t72nzm7antmht0mtjyt7ylym4wmt8ap

I want to track transaction history when I press view all it directs me to mintscan.io osmo and I don't see history or tx hash of transactions I did on Sinfonia testnet. explorer is very important to test, because transaction history is stored properly and makes it easy to check tx hashes. if there is a problem in the transaction. this is my opinion.
bitsong13yez56pph5qnajftfhfnrquqcyl87zxepsuk5w

We need to reduce the minimum length for Fan Tokens symbol to 2.

This could suit the requests for some specific symbols like D9 (Delta 9).

bitsong160z0dte5mtaxcug8jwgkw3wx39qv0xj0ey5mh9

Add following commands in the Makefile
build-docker-go-bitsong
localnet-start
localnet-stop

When sending transaction through bitsongcli, and instead of y/N just pressing enter - the below error

goroutine 1 [running]:
github.com/cosmos/cosmos-sdk/client/input.GetConfirmation(0xff28e1, 0x33, 0xc0009e7090, 0xc0000f9000, 0xc0009e7018, 0x1)
        /root/go/pkg/mod/github.com/cosmos/[email protected]/client/input/input.go:78 +0x1d9
github.com/cosmos/cosmos-sdk/x/auth/client/utils.CompleteAndBroadcastTxCLI(0xc00093e7d0, 0x1310280, 0xc000944700, 0x2ea, 0x0, 0x30d40, 0x3ff0000000000000, 0x0, 0x7ffc1ad9a78c, 0x11, ...)
        /root/go/pkg/mod/github.com/cosmos/[email protected]/x/auth/client/utils/tx.go:89 +0x995
github.com/cosmos/cosmos-sdk/x/auth/client/utils.GenerateOrBroadcastMsgs(0xc0000f48c0, 0x1316080, 0xc00086dec0, 0x0, 0x0, 0x12e28c0, 0xc000010018, 0xfbe5ce, 0x4, 0x0, ...)
        /root/go/pkg/mod/github.com/cosmos/[email protected]/x/auth/client/utils/tx.go:40 +0x15c
github.com/cosmos/cosmos-sdk/x/staking/client/cli.GetCmdCreateValidator.func1(0xc000887680, 0xc000986990, 0x0, 0x9, 0x0, 0x0)
        /root/go/pkg/mod/github.com/cosmos/[email protected]/x/staking/client/cli/tx.go:60 +0x23e
github.com/spf13/cobra.(*Command).execute(0xc000887680, 0xc000986900, 0x9, 0x9, 0xc000887680, 0xc000986900)
        /root/go/pkg/mod/github.com/spf13/[email protected]/command.go:826 +0x460
github.com/spf13/cobra.(*Command).ExecuteC(0xc0000b6c80, 0x86b0c0, 0xc0000b6c80, 0xfbd5e6)
        /root/go/pkg/mod/github.com/spf13/[email protected]/command.go:914 +0x2fb
github.com/spf13/cobra.(*Command).Execute(...)
        /root/go/pkg/mod/github.com/spf13/[email protected]/command.go:864
github.com/tendermint/tendermint/libs/cli.Executor.Execute(0xc0000b6c80, 0x11b56b8, 0x2, 0xc000035c60)
        /root/go/pkg/mod/github.com/tendermint/[email protected]/libs/cli/setup.go:89 +0x3c
main.main()
        /root/go-bitsong/cmd/bitsongcli/main.go:77 +0x59d

I can not add liquidity D9/BTSG pool for the fist time. The second time it is ok.
My wallet : bitsong187z3p9p8dqt6w2y0cs9k53yrus4gjs3jll2pes

Description:

• Develop a terraform provider plugin for BitSong to initialize a new cluster based on existing cosmos-sdk scripts.
• Check the branch feature/terraform, navigate into /networks/ and test all the scripts and the remote directory.
• Setup a new cluster on AWS and DO, test the environment and change the configuration when need.
• If you need more details on what exactly we are looking for, please message our core engineers in Discord via #gitcoin

Submission Requirements:

• Share link to open source code via Github (make sure you are in feature/terraform branch)
• Document the solution with the steps to recreate (small tutorial in README)
• Submit link to working cluster
• Contribute via Gitcoin

Resources:

• More info on how to install BitSong
• Follow steps on how to use BitSong
• Talk to our core engineers on Discord via #gitcoin

Bounty:

• 250 DAI

Submission Deadline:

• June 18th

Judging Commencement:

• June 20st

Bounty Recipients Announced:

• June 30th

The command bitsongd tx fantoken use the description Token transaction subcommands

It should be FanToken transaction subcommands

i have used all the features and i found a problem while doing the transaction,,,
transactions more than once always fail, and have to refresh again
and try again the transaction then it works, I think its a bug, hope this problem can be fixed before mainet

notifies that LOBO tokens are not visible in assets. please fix it soon

when I first tried the swap feature, there was a slight bug, namely the swap failed, and to solve that problem every time I wanted to swap or make a transaction I refreshed the web page,,, and everything was normal and smooth, thank you
this is my address
bitsong1wqm3h0sc9zujeq4zn7ewhsvy6tgj3mcsgud5yv

Add the flag --mintable in the example of bitsongd tx fantoken issue

Examples:
$ bitsongd tx token issue --name="Kitty Token" --symbol="kitty" --max-supply="1000000000000" --issue-fee="1000000" --description="Kitty Token" --mintable true --from=<key-name> --chain-id=<chain-id> --fees=<fee>

I think the selection of icons such as swap, add liquidity and transfer should be in the main menu to make it look easier and simpler... and my suggestion is that the color selection in the bounds is very faint and almost invisible, it would be better if you did that color change

i can't do swap on sp 1% & 3% but sp 5% works. please fix.
my address : bitsong13yez56pph5qnajftfhfnrquqcyl87zxepsuk5w

Description

• I have 2 kinds of BTSG tokens, each of which has a balance, but when I connect the wallet no balance is displayed, I've refreshed the page and the results are the same, maybe this is the first step that the developer must fix

Screenshot

Suggestion

• maybe the newly created token is not connected between the wallet and the web
• Check code between BTSG token to Sinfonia web ( Maybe have fail )

The slashing condition for uptime is 0.5 x 100 blocks which is less than 10mins to be jailed at start, 5mins after the first 100 blocks.

I want to see the transactions that I have made, on the testnet web image below there are several failed transactions and only marked with the words "broadcasting" . then I pressed the view all button and entered the mintscan.io web from osmosis, but I looked down in the transaction section there was no transaction record at all and it was shown in the image 2 below. then i checked in the keplr wallet there was a token transaction on osmosis testnet it was shown in the image 3 below.

fix this bug, all transactions should be recorded clearly and if it fails the failure should be clearly written on webscan or mintscan.io/osmosis and also written "failed" in the transaction history in the swap menu. and please if the transaction fails, put a mark in the transaction section as "failed" not "broadcasting", if it is written broadcasting it means the transaction is still running but not failed.

I'm confused why there are no transactions written on the mintscan.io web/osmosis, even though the button "view all" goes directly to that web ??

is there any typo coding for the click of a button that goes straight to the web?
or indeed the transaction is not written on mintscan.io/osmosis? but it written on another web scan?
please check it again ...

this my wallet bitsong testnet :
bitsong1e7tpgjy8kfvfsm4f7uypjvsw9hfdqsustpwvm8

this my wallet osmosis :
osmo1pe9gx7yzuzuw8qw60hnhscz2n9p6m2nlwdqu72

In transfering screen, if available asset is zero; amount looks -0.025

My adress: bitsong1djytet30fzdf8cq0tm7wx8m8kw8qfzuw7my2hs

LIST OF BUGS I FOUND FROM 104.21.7.58 / testnet.sinfonia.zone
Device for Testing : Macbook M1 Pro
Tool : Openvas and NMAP

1. TCP Port Opened ( scanned by nmap 104.21.7.58 )
   List port opened : 80,2052,443,2053,2082,2083,2086,2087,2095,8080,2096,8443,8880
   Level Bug : Medium
   Detail : An open port may be an expected configuration. For example, web servers use port 80 to serve websites over http and port 443 to serve websites over https. For a list of commonly used ports see https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers.
   An unexpected open port could give unintended access to applications, data, and private networks. Open ports can also be dangerous when expected services are out of date and exploited through security vulnerabilities.
   Solution : Close the port
2. Application Error Disclosure
   Link Issue : https://testnet.sinfonia.zone/assets/index.8e544d33.js
   Level Bug : Medium
   CWE Id : 200
   Detail : This page contains an error/warning message that may disclose sensitive information like the location of the file that produced the unhandled exception. This information can be used to launch further attacks against the web application. The alert could be a false positive if the error message is found inside a documentation page.
   Solution : Review the source code of this page. Implement custom error pages. Consider implementing a mechanism to provide a unique error reference/identifier to the client (browser) while logging the details on the server side and not exposing them to the user.
3. Cross Domain Missconfiguration
   Level bug : medium
   CWE id : 264
   Detail : Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server
   Solution : Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
   Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.
   Reference : https://vulncat.fortify.com/en/detail?id=desc.config.dotnet.html5_overly_permissive_cors_policy
4. Missing Anti-clickjacking Header
   Level Bug : Medium
   CWE id : 1021
   Detail : The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against 'ClickJacking' attacks.
   Solution : Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.
   If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.
   Reference : https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options

more issue and bug on bitsong you can check here

• Add testnet command
• Add testnet genesis

When you issue a new fantoken, you need to specify the symbol. In my example I issued the symbol angelo it mean that in the state it's stored as uangelo.

bitsongd tx fantoken issue --name Angelo --symbol angelo --max-supply 1000 --issue-fee 1000000

If you want to mint a new fantoken, you must specify the symbol, the current command is accepting the denom and it should be changed with symbol

From:
bitsongd tx fantoken mint uangelo --recipient $(bitsongd keys show validator -a) --amount 1

To:
bitsongd tx fantoken mint angelo --recipient $(bitsongd keys show validator -a) --amount 1

From:
bitsongd tx fantoken burn uangelo --amount 1

To:
bitsongd tx fantoken burn angelo --amount 1

Change the following description

Command:
bitsongd tx fantoken transfer

From:
bitsongd tx token transfer <symbol> --to=<to> --from=<key-name> --chain-id=<chain-id> --fees=<fee>

To:
bitsongd tx fantoken transfer <symbol> --to=<to> --from=<key-name> --chain-id=<chain-id> --fees=<fee>