Proposal AI

Proposal AI

curl --request POST \
  --url https://api.syncgovhub.com/api/proposal/ai \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --data '
{
  "query": "<string>",
  "govaction_id": "<string>"
}
'

import requests

url = "https://api.syncgovhub.com/api/proposal/ai"

payload = {
    "query": "<string>",
    "govaction_id": "<string>"
}
headers = {
    "x-api-key": "<x-api-key>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

const options = {
  method: 'POST',
  headers: {'x-api-key': '<x-api-key>', 'Content-Type': 'application/json'},
  body: JSON.stringify({query: '<string>', govaction_id: '<string>'})
};

fetch('https://api.syncgovhub.com/api/proposal/ai', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.syncgovhub.com/api/proposal/ai",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_POSTFIELDS => json_encode([
    'query' => '<string>',
    'govaction_id' => '<string>'
  ]),
  CURLOPT_HTTPHEADER => [
    "Content-Type: application/json",
    "x-api-key: <x-api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://api.syncgovhub.com/api/proposal/ai"

	payload := strings.NewReader("{\n  \"query\": \"<string>\",\n  \"govaction_id\": \"<string>\"\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("x-api-key", "<x-api-key>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.post("https://api.syncgovhub.com/api/proposal/ai")
  .header("x-api-key", "<x-api-key>")
  .header("Content-Type", "application/json")
  .body("{\n  \"query\": \"<string>\",\n  \"govaction_id\": \"<string>\"\n}")
  .asString();

require 'uri'
require 'net/http'

url = URI("https://api.syncgovhub.com/api/proposal/ai")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["x-api-key"] = '<x-api-key>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"query\": \"<string>\",\n  \"govaction_id\": \"<string>\"\n}"

response = http.request(request)
puts response.read_body

{
  "data": {
    "analysis": "## Parameter Change Analysis\n\nThis proposal suggests modifying the protocol parameter `minPoolCost` from 340 ADA to 170 ADA. This parameter sets the minimum fixed cost that stake pool operators (SPOs) can charge for operating a pool.\n\n### Main Objectives\n\nThe primary goal of this proposal is to lower the entry barrier for new stake pool operators by reducing the minimum fixed cost requirement by 50%. This change aims to enhance decentralization by making it more economically viable to operate smaller stake pools.\n\n### Technical Implications\n\nThe `minPoolCost` parameter directly affects stake pool economics in the following ways:\n\n1. **Pool Profitability**: Reducing this parameter allows pool operators to set lower fixed costs, potentially making smaller pools more competitive\n2. **Delegator Rewards**: Lower fixed costs could translate to higher returns for delegators of smaller pools\n3. **Network Topology**: The change may encourage the creation of more pools, potentially increasing network decentralization\n\n### Community Sentiment\n\nThe proposal received strong support from the DRep community, with 87.2% voting in favor. SPOs were more divided with 62.4% in favor, suggesting some existing operators have concerns about increased competition or potential impacts on the sustainability of smaller pools.\n\nThe total voting participation was high at 78.3%, indicating significant community interest in this parameter change.",
    "proposal_id": "gov1x8jkz74",
    "proposal_title": "Reduce minPoolCost Parameter from 340 to 170 ADA",
    "proposal_type": "ParameterChange",
    "proposal_subtype": "Economic"
  },
  "meta": {
    "query": "What are the main objectives and implications of this parameter change?",
    "content_sources": [
      {
        "url": "https://governance.cardano.org/en/proposals/gov1x8jkz74",
        "is_meta_url": true,
        "content_type": "proposal"
      },
      {
        "url": "https://github.com/cardano-foundation/cips/blob/master/CIP-0094/README.md",
        "is_meta_url": false,
        "content_type": "technical-reference"
      },
      {
        "url": "https://forum.cardano.org/t/discussion-reduce-minpoolcost-parameter-from-340-to-170-ada/128975",
        "is_meta_url": false,
        "content_type": "discussion"
      }
    ],
    "timings": {
      "fetch_proposal_data": 125,
      "search_content": 452,
      "openai_analysis": 2351,
      "total": 2928
    }
  }
}

{
  "data": {
    "analysis": "## Parameter Change Proposals - Common Patterns\n\nBased on the analysis of parameter change proposals in the Cardano governance system, several key patterns emerge:\n\n### 1. Economic Parameter Changes\n\nThe most common parameter modifications focus on economic aspects of the protocol:\n\n- **Pool Economics**: Adjustments to `minPoolCost` and `poolPledgeInfluence` parameters are frequent, aiming to balance pool operator sustainability with delegator returns\n- **Transaction Costs**: Changes to `minFeeA`, `minFeeB`, and related parameters to optimize transaction pricing\n- **Monetary Policy**: Fine-tuning of staking rewards and incentive mechanisms\n\n### 2. Technical Parameter Changes\n\nTechnical parameters are typically adjusted in response to network performance or security considerations:\n\n- **Block Size**: Gradual increases to `maxBlockSize` to improve throughput as network capacity grows\n- **Script Limits**: Adjustments to script execution limits to balance computational constraints with dApp functionality\n- **Protocol Security**: Conservative modifications to security parameters with extensive testing evidence\n\n### 3. Governance Parameters\n\nChanges to governance rules themselves represent a smaller but significant category:\n\n- **Voting Thresholds**: Adjustments to participation thresholds and majority requirements\n- **DRep Mechanics**: Refinements to delegation and voting power calculations\n\n### Common Success Factors\n\nSuccessful parameter change proposals typically share these characteristics:\n\n1. Clear technical justification with empirical evidence\n2. Gradual rather than radical parameter adjustments\n3. Thorough impact analysis discussing potential trade-offs\n4. Active engagement with community feedback during drafting\n5. Transparent benchmarking data when performance claims are made\n\nProposals lacking these elements tend to receive less support or face significant opposition during voting."
  },
  "meta": {
    "query": "What are the common patterns in parameter change proposals?",
    "content_sources": [
      {
        "url": "https://governance.cardano.org/en/proposals/",
        "is_meta_url": false,
        "content_type": "proposal-list"
      },
      {
        "url": "https://github.com/cardano-foundation/cips/tree/master/",
        "is_meta_url": false,
        "content_type": "technical-reference"
      },
      {
        "url": "https://forum.cardano.org/c/governance/29",
        "is_meta_url": false,
        "content_type": "discussion"
      }
    ],
    "timings": {
      "fetch_proposal_data": 320,
      "search_content": 865,
      "openai_analysis": 2758,
      "total": 3943
    }
  }
}

{
  "data": {
    "analysis": "# Analysis of ARTICLE IV. THE CARDANO BLOCKCHAIN ECOSYSTEM BUDGET\n\n## Overview\nARTICLE IV of the Cardano Blockchain Constitution pertains to the ecosystem budget, which is a crucial component in the governance and economic framework of Cardano. This section outlines the principles and processes related to the allocation and management of funds within the Cardano ecosystem.\n\n## Key Sections and Content\n\n### Section 1: Budget Proposals\n- **Proposal Submission**: Any participant in the Cardano Community is allowed to propose a budget for the ecosystem. This inclusivity ensures that all stakeholders have the opportunity to influence financial decisions.\n- **Community Involvement**: The section emphasizes the role of the community in shaping the budget, reflecting Cardano's commitment to decentralized governance.\n\n### Section 2: Budget Approval\n- **Approval Process**: Details the process by which budget proposals are reviewed and approved. This typically involves a voting mechanism where community members can express their support or opposition.\n- **Transparency and Accountability**: The section likely includes measures to ensure that the budget approval process is transparent and that those responsible for managing funds are held accountable.\n\n### Section 3: Fund Allocation\n- **Allocation Criteria**: Specifies the criteria used to allocate funds to various projects or initiatives within the ecosystem. This ensures that resources are directed towards efforts that align with Cardano's strategic goals.\n- **Prioritization**: May include guidelines on how to prioritize different funding requests based on factors such as impact, feasibility, and alignment with community values.\n\n### Section 4: Monitoring and Reporting\n- **Oversight Mechanisms**: Describes the mechanisms in place to monitor the use of funds and ensure they are used effectively. This could involve regular reporting and audits.\n- **Feedback Loops**: Encourages continuous feedback from the community to improve budget management practices.\n\n### Section 5: Amendments and Revisions\n- **Flexibility**: Allows for amendments to the budget process to adapt to changing needs and circumstances within the Cardano ecosystem.\n- **Community Engagement**: Ensures that any changes to the budget process involve community consultation and consensus.\n\n## Conclusion\nARTICLE IV of the Cardano Blockchain Constitution establishes a comprehensive framework for managing the ecosystem budget, emphasizing transparency, community involvement, and accountability. This framework is designed to ensure that financial resources are allocated efficiently and in a manner that supports the long-term sustainability and growth of the Cardano ecosystem.\n\nFor more detailed information, refer to the specific sections of the draft constitution available at the provided GitHub links.",
    "proposal_id": "gov_action1js2s9v92zpxg2rge0y3jt9zy626he2m67x9kx9phw4r942kvsn6sqfym0d7",
    "proposal_title": "Decrease Treasury Tax from 20% to 10%",
    "proposal_type": "ParameterChange",
    "proposal_subtype": "Economic"
  },
  "meta": {
    "query": "ARTICLE IV. THE CARDANO BLOCKCHAIN ECOSYSTEM",
    "content_sources": [
      {
        "url": "https://github.com/IntersectMBO/draft-constitution/blob/main/2024-12-05/draft-constitution-converted.md",
        "is_meta_url": false,
        "content_type": "markdown"
      },
      {
        "url": "https://github.com/IntersectMBO/draft-constitution/blob/main/2024-12-04/draft-constitution-converted.md",
        "is_meta_url": false,
        "content_type": "markdown"
      }
    ],
    "timings": {
      "fetch_proposal_data": 344,
      "search_content": 231,
      "openai_analysis": 12807,
      "total": 13383
    }
  }
}

{
  "error": "Missing or invalid query",
  "details": "Please provide a valid query string"
}

{
  "error": "Unauthorized",
  "message": "API key is required"
}

{
  "error": "Proposal not found",
  "details": "No proposal found with ID: gov1x8jkz74"
}

{
  "error": "Failed to process enhanced AI analysis request",
  "details": "Internal server error occurred while processing the request"
}

POST

api

proposal

Proposal AI

curl --request POST \
  --url https://api.syncgovhub.com/api/proposal/ai \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --data '
{
  "query": "<string>",
  "govaction_id": "<string>"
}
'

import requests

url = "https://api.syncgovhub.com/api/proposal/ai"

payload = {
    "query": "<string>",
    "govaction_id": "<string>"
}
headers = {
    "x-api-key": "<x-api-key>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

const options = {
  method: 'POST',
  headers: {'x-api-key': '<x-api-key>', 'Content-Type': 'application/json'},
  body: JSON.stringify({query: '<string>', govaction_id: '<string>'})
};

fetch('https://api.syncgovhub.com/api/proposal/ai', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.syncgovhub.com/api/proposal/ai",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_POSTFIELDS => json_encode([
    'query' => '<string>',
    'govaction_id' => '<string>'
  ]),
  CURLOPT_HTTPHEADER => [
    "Content-Type: application/json",
    "x-api-key: <x-api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://api.syncgovhub.com/api/proposal/ai"

	payload := strings.NewReader("{\n  \"query\": \"<string>\",\n  \"govaction_id\": \"<string>\"\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("x-api-key", "<x-api-key>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.post("https://api.syncgovhub.com/api/proposal/ai")
  .header("x-api-key", "<x-api-key>")
  .header("Content-Type", "application/json")
  .body("{\n  \"query\": \"<string>\",\n  \"govaction_id\": \"<string>\"\n}")
  .asString();

require 'uri'
require 'net/http'

url = URI("https://api.syncgovhub.com/api/proposal/ai")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["x-api-key"] = '<x-api-key>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"query\": \"<string>\",\n  \"govaction_id\": \"<string>\"\n}"

response = http.request(request)
puts response.read_body

{
  "data": {
    "analysis": "## Parameter Change Analysis\n\nThis proposal suggests modifying the protocol parameter `minPoolCost` from 340 ADA to 170 ADA. This parameter sets the minimum fixed cost that stake pool operators (SPOs) can charge for operating a pool.\n\n### Main Objectives\n\nThe primary goal of this proposal is to lower the entry barrier for new stake pool operators by reducing the minimum fixed cost requirement by 50%. This change aims to enhance decentralization by making it more economically viable to operate smaller stake pools.\n\n### Technical Implications\n\nThe `minPoolCost` parameter directly affects stake pool economics in the following ways:\n\n1. **Pool Profitability**: Reducing this parameter allows pool operators to set lower fixed costs, potentially making smaller pools more competitive\n2. **Delegator Rewards**: Lower fixed costs could translate to higher returns for delegators of smaller pools\n3. **Network Topology**: The change may encourage the creation of more pools, potentially increasing network decentralization\n\n### Community Sentiment\n\nThe proposal received strong support from the DRep community, with 87.2% voting in favor. SPOs were more divided with 62.4% in favor, suggesting some existing operators have concerns about increased competition or potential impacts on the sustainability of smaller pools.\n\nThe total voting participation was high at 78.3%, indicating significant community interest in this parameter change.",
    "proposal_id": "gov1x8jkz74",
    "proposal_title": "Reduce minPoolCost Parameter from 340 to 170 ADA",
    "proposal_type": "ParameterChange",
    "proposal_subtype": "Economic"
  },
  "meta": {
    "query": "What are the main objectives and implications of this parameter change?",
    "content_sources": [
      {
        "url": "https://governance.cardano.org/en/proposals/gov1x8jkz74",
        "is_meta_url": true,
        "content_type": "proposal"
      },
      {
        "url": "https://github.com/cardano-foundation/cips/blob/master/CIP-0094/README.md",
        "is_meta_url": false,
        "content_type": "technical-reference"
      },
      {
        "url": "https://forum.cardano.org/t/discussion-reduce-minpoolcost-parameter-from-340-to-170-ada/128975",
        "is_meta_url": false,
        "content_type": "discussion"
      }
    ],
    "timings": {
      "fetch_proposal_data": 125,
      "search_content": 452,
      "openai_analysis": 2351,
      "total": 2928
    }
  }
}

{
  "data": {
    "analysis": "## Parameter Change Proposals - Common Patterns\n\nBased on the analysis of parameter change proposals in the Cardano governance system, several key patterns emerge:\n\n### 1. Economic Parameter Changes\n\nThe most common parameter modifications focus on economic aspects of the protocol:\n\n- **Pool Economics**: Adjustments to `minPoolCost` and `poolPledgeInfluence` parameters are frequent, aiming to balance pool operator sustainability with delegator returns\n- **Transaction Costs**: Changes to `minFeeA`, `minFeeB`, and related parameters to optimize transaction pricing\n- **Monetary Policy**: Fine-tuning of staking rewards and incentive mechanisms\n\n### 2. Technical Parameter Changes\n\nTechnical parameters are typically adjusted in response to network performance or security considerations:\n\n- **Block Size**: Gradual increases to `maxBlockSize` to improve throughput as network capacity grows\n- **Script Limits**: Adjustments to script execution limits to balance computational constraints with dApp functionality\n- **Protocol Security**: Conservative modifications to security parameters with extensive testing evidence\n\n### 3. Governance Parameters\n\nChanges to governance rules themselves represent a smaller but significant category:\n\n- **Voting Thresholds**: Adjustments to participation thresholds and majority requirements\n- **DRep Mechanics**: Refinements to delegation and voting power calculations\n\n### Common Success Factors\n\nSuccessful parameter change proposals typically share these characteristics:\n\n1. Clear technical justification with empirical evidence\n2. Gradual rather than radical parameter adjustments\n3. Thorough impact analysis discussing potential trade-offs\n4. Active engagement with community feedback during drafting\n5. Transparent benchmarking data when performance claims are made\n\nProposals lacking these elements tend to receive less support or face significant opposition during voting."
  },
  "meta": {
    "query": "What are the common patterns in parameter change proposals?",
    "content_sources": [
      {
        "url": "https://governance.cardano.org/en/proposals/",
        "is_meta_url": false,
        "content_type": "proposal-list"
      },
      {
        "url": "https://github.com/cardano-foundation/cips/tree/master/",
        "is_meta_url": false,
        "content_type": "technical-reference"
      },
      {
        "url": "https://forum.cardano.org/c/governance/29",
        "is_meta_url": false,
        "content_type": "discussion"
      }
    ],
    "timings": {
      "fetch_proposal_data": 320,
      "search_content": 865,
      "openai_analysis": 2758,
      "total": 3943
    }
  }
}

{
  "data": {
    "analysis": "# Analysis of ARTICLE IV. THE CARDANO BLOCKCHAIN ECOSYSTEM BUDGET\n\n## Overview\nARTICLE IV of the Cardano Blockchain Constitution pertains to the ecosystem budget, which is a crucial component in the governance and economic framework of Cardano. This section outlines the principles and processes related to the allocation and management of funds within the Cardano ecosystem.\n\n## Key Sections and Content\n\n### Section 1: Budget Proposals\n- **Proposal Submission**: Any participant in the Cardano Community is allowed to propose a budget for the ecosystem. This inclusivity ensures that all stakeholders have the opportunity to influence financial decisions.\n- **Community Involvement**: The section emphasizes the role of the community in shaping the budget, reflecting Cardano's commitment to decentralized governance.\n\n### Section 2: Budget Approval\n- **Approval Process**: Details the process by which budget proposals are reviewed and approved. This typically involves a voting mechanism where community members can express their support or opposition.\n- **Transparency and Accountability**: The section likely includes measures to ensure that the budget approval process is transparent and that those responsible for managing funds are held accountable.\n\n### Section 3: Fund Allocation\n- **Allocation Criteria**: Specifies the criteria used to allocate funds to various projects or initiatives within the ecosystem. This ensures that resources are directed towards efforts that align with Cardano's strategic goals.\n- **Prioritization**: May include guidelines on how to prioritize different funding requests based on factors such as impact, feasibility, and alignment with community values.\n\n### Section 4: Monitoring and Reporting\n- **Oversight Mechanisms**: Describes the mechanisms in place to monitor the use of funds and ensure they are used effectively. This could involve regular reporting and audits.\n- **Feedback Loops**: Encourages continuous feedback from the community to improve budget management practices.\n\n### Section 5: Amendments and Revisions\n- **Flexibility**: Allows for amendments to the budget process to adapt to changing needs and circumstances within the Cardano ecosystem.\n- **Community Engagement**: Ensures that any changes to the budget process involve community consultation and consensus.\n\n## Conclusion\nARTICLE IV of the Cardano Blockchain Constitution establishes a comprehensive framework for managing the ecosystem budget, emphasizing transparency, community involvement, and accountability. This framework is designed to ensure that financial resources are allocated efficiently and in a manner that supports the long-term sustainability and growth of the Cardano ecosystem.\n\nFor more detailed information, refer to the specific sections of the draft constitution available at the provided GitHub links.",
    "proposal_id": "gov_action1js2s9v92zpxg2rge0y3jt9zy626he2m67x9kx9phw4r942kvsn6sqfym0d7",
    "proposal_title": "Decrease Treasury Tax from 20% to 10%",
    "proposal_type": "ParameterChange",
    "proposal_subtype": "Economic"
  },
  "meta": {
    "query": "ARTICLE IV. THE CARDANO BLOCKCHAIN ECOSYSTEM",
    "content_sources": [
      {
        "url": "https://github.com/IntersectMBO/draft-constitution/blob/main/2024-12-05/draft-constitution-converted.md",
        "is_meta_url": false,
        "content_type": "markdown"
      },
      {
        "url": "https://github.com/IntersectMBO/draft-constitution/blob/main/2024-12-04/draft-constitution-converted.md",
        "is_meta_url": false,
        "content_type": "markdown"
      }
    ],
    "timings": {
      "fetch_proposal_data": 344,
      "search_content": 231,
      "openai_analysis": 12807,
      "total": 13383
    }
  }
}

{
  "error": "Missing or invalid query",
  "details": "Please provide a valid query string"
}

{
  "error": "Unauthorized",
  "message": "API key is required"
}

{
  "error": "Proposal not found",
  "details": "No proposal found with ID: gov1x8jkz74"
}

{
  "error": "Failed to process enhanced AI analysis request",
  "details": "Internal server error occurred while processing the request"
}

Intelligent Analysis: This endpoint provides detailed, context-aware answers to questions about specific governance proposals or general proposal patterns using advanced AI.

The Proposal API enables you to ask natural language questions about Cardano governance proposals and receive detailed analysis based on the proposal content, metadata, and related documents. It can analyze specific proposals or provide insights on patterns across multiple proposals.

Request Headers

string

required

Your API key for authentication

Request Body

string

required

Natural language question about a proposal

string

ID of the specific proposal to analyze. If omitted, the API will analyze across all proposals.

Response

object

Show Properties

string

AI-generated analysis responding to the query

string

ID of the analyzed proposal (if govaction_id was provided)

string

Title of the analyzed proposal (if govaction_id was provided)

string

Type of the analyzed proposal (if govaction_id was provided)

string

Subtype of the analyzed proposal, if applicable (if govaction_id was provided)

object

Show Properties

string

Original query string

array

Sources of content used in the analysis

Show Content Source

string

URL of the content source

boolean

Whether this is the primary metadata URL

string

Type of content (e.g., “proposal”, “discussion”, “technical-reference”, “markdown”)

object

Performance metrics for the request

Show Properties

number

Time taken to fetch proposal data (ms)

number

Time taken to search relevant content (ms)

number

Time taken for AI analysis (ms)

number

Total request processing time (ms)

{
  "data": {
    "analysis": "## Parameter Change Analysis\n\nThis proposal suggests modifying the protocol parameter `minPoolCost` from 340 ADA to 170 ADA. This parameter sets the minimum fixed cost that stake pool operators (SPOs) can charge for operating a pool.\n\n### Main Objectives\n\nThe primary goal of this proposal is to lower the entry barrier for new stake pool operators by reducing the minimum fixed cost requirement by 50%. This change aims to enhance decentralization by making it more economically viable to operate smaller stake pools.\n\n### Technical Implications\n\nThe `minPoolCost` parameter directly affects stake pool economics in the following ways:\n\n1. **Pool Profitability**: Reducing this parameter allows pool operators to set lower fixed costs, potentially making smaller pools more competitive\n2. **Delegator Rewards**: Lower fixed costs could translate to higher returns for delegators of smaller pools\n3. **Network Topology**: The change may encourage the creation of more pools, potentially increasing network decentralization\n\n### Community Sentiment\n\nThe proposal received strong support from the DRep community, with 87.2% voting in favor. SPOs were more divided with 62.4% in favor, suggesting some existing operators have concerns about increased competition or potential impacts on the sustainability of smaller pools.\n\nThe total voting participation was high at 78.3%, indicating significant community interest in this parameter change.",
    "proposal_id": "gov1x8jkz74",
    "proposal_title": "Reduce minPoolCost Parameter from 340 to 170 ADA",
    "proposal_type": "ParameterChange",
    "proposal_subtype": "Economic"
  },
  "meta": {
    "query": "What are the main objectives and implications of this parameter change?",
    "content_sources": [
      {
        "url": "https://governance.cardano.org/en/proposals/gov1x8jkz74",
        "is_meta_url": true,
        "content_type": "proposal"
      },
      {
        "url": "https://github.com/cardano-foundation/cips/blob/master/CIP-0094/README.md",
        "is_meta_url": false,
        "content_type": "technical-reference"
      },
      {
        "url": "https://forum.cardano.org/t/discussion-reduce-minpoolcost-parameter-from-340-to-170-ada/128975",
        "is_meta_url": false,
        "content_type": "discussion"
      }
    ],
    "timings": {
      "fetch_proposal_data": 125,
      "search_content": 452,
      "openai_analysis": 2351,
      "total": 2928
    }
  }
}

{
  "data": {
    "analysis": "## Parameter Change Proposals - Common Patterns\n\nBased on the analysis of parameter change proposals in the Cardano governance system, several key patterns emerge:\n\n### 1. Economic Parameter Changes\n\nThe most common parameter modifications focus on economic aspects of the protocol:\n\n- **Pool Economics**: Adjustments to `minPoolCost` and `poolPledgeInfluence` parameters are frequent, aiming to balance pool operator sustainability with delegator returns\n- **Transaction Costs**: Changes to `minFeeA`, `minFeeB`, and related parameters to optimize transaction pricing\n- **Monetary Policy**: Fine-tuning of staking rewards and incentive mechanisms\n\n### 2. Technical Parameter Changes\n\nTechnical parameters are typically adjusted in response to network performance or security considerations:\n\n- **Block Size**: Gradual increases to `maxBlockSize` to improve throughput as network capacity grows\n- **Script Limits**: Adjustments to script execution limits to balance computational constraints with dApp functionality\n- **Protocol Security**: Conservative modifications to security parameters with extensive testing evidence\n\n### 3. Governance Parameters\n\nChanges to governance rules themselves represent a smaller but significant category:\n\n- **Voting Thresholds**: Adjustments to participation thresholds and majority requirements\n- **DRep Mechanics**: Refinements to delegation and voting power calculations\n\n### Common Success Factors\n\nSuccessful parameter change proposals typically share these characteristics:\n\n1. Clear technical justification with empirical evidence\n2. Gradual rather than radical parameter adjustments\n3. Thorough impact analysis discussing potential trade-offs\n4. Active engagement with community feedback during drafting\n5. Transparent benchmarking data when performance claims are made\n\nProposals lacking these elements tend to receive less support or face significant opposition during voting."
  },
  "meta": {
    "query": "What are the common patterns in parameter change proposals?",
    "content_sources": [
      {
        "url": "https://governance.cardano.org/en/proposals/",
        "is_meta_url": false,
        "content_type": "proposal-list"
      },
      {
        "url": "https://github.com/cardano-foundation/cips/tree/master/",
        "is_meta_url": false,
        "content_type": "technical-reference"
      },
      {
        "url": "https://forum.cardano.org/c/governance/29",
        "is_meta_url": false,
        "content_type": "discussion"
      }
    ],
    "timings": {
      "fetch_proposal_data": 320,
      "search_content": 865,
      "openai_analysis": 2758,
      "total": 3943
    }
  }
}

{
  "data": {
    "analysis": "# Analysis of ARTICLE IV. THE CARDANO BLOCKCHAIN ECOSYSTEM BUDGET\n\n## Overview\nARTICLE IV of the Cardano Blockchain Constitution pertains to the ecosystem budget, which is a crucial component in the governance and economic framework of Cardano. This section outlines the principles and processes related to the allocation and management of funds within the Cardano ecosystem.\n\n## Key Sections and Content\n\n### Section 1: Budget Proposals\n- **Proposal Submission**: Any participant in the Cardano Community is allowed to propose a budget for the ecosystem. This inclusivity ensures that all stakeholders have the opportunity to influence financial decisions.\n- **Community Involvement**: The section emphasizes the role of the community in shaping the budget, reflecting Cardano's commitment to decentralized governance.\n\n### Section 2: Budget Approval\n- **Approval Process**: Details the process by which budget proposals are reviewed and approved. This typically involves a voting mechanism where community members can express their support or opposition.\n- **Transparency and Accountability**: The section likely includes measures to ensure that the budget approval process is transparent and that those responsible for managing funds are held accountable.\n\n### Section 3: Fund Allocation\n- **Allocation Criteria**: Specifies the criteria used to allocate funds to various projects or initiatives within the ecosystem. This ensures that resources are directed towards efforts that align with Cardano's strategic goals.\n- **Prioritization**: May include guidelines on how to prioritize different funding requests based on factors such as impact, feasibility, and alignment with community values.\n\n### Section 4: Monitoring and Reporting\n- **Oversight Mechanisms**: Describes the mechanisms in place to monitor the use of funds and ensure they are used effectively. This could involve regular reporting and audits.\n- **Feedback Loops**: Encourages continuous feedback from the community to improve budget management practices.\n\n### Section 5: Amendments and Revisions\n- **Flexibility**: Allows for amendments to the budget process to adapt to changing needs and circumstances within the Cardano ecosystem.\n- **Community Engagement**: Ensures that any changes to the budget process involve community consultation and consensus.\n\n## Conclusion\nARTICLE IV of the Cardano Blockchain Constitution establishes a comprehensive framework for managing the ecosystem budget, emphasizing transparency, community involvement, and accountability. This framework is designed to ensure that financial resources are allocated efficiently and in a manner that supports the long-term sustainability and growth of the Cardano ecosystem.\n\nFor more detailed information, refer to the specific sections of the draft constitution available at the provided GitHub links.",
    "proposal_id": "gov_action1js2s9v92zpxg2rge0y3jt9zy626he2m67x9kx9phw4r942kvsn6sqfym0d7",
    "proposal_title": "Decrease Treasury Tax from 20% to 10%",
    "proposal_type": "ParameterChange",
    "proposal_subtype": "Economic"
  },
  "meta": {
    "query": "ARTICLE IV. THE CARDANO BLOCKCHAIN ECOSYSTEM",
    "content_sources": [
      {
        "url": "https://github.com/IntersectMBO/draft-constitution/blob/main/2024-12-05/draft-constitution-converted.md",
        "is_meta_url": false,
        "content_type": "markdown"
      },
      {
        "url": "https://github.com/IntersectMBO/draft-constitution/blob/main/2024-12-04/draft-constitution-converted.md",
        "is_meta_url": false,
        "content_type": "markdown"
      }
    ],
    "timings": {
      "fetch_proposal_data": 344,
      "search_content": 231,
      "openai_analysis": 12807,
      "total": 13383
    }
  }
}

{
  "error": "Missing or invalid query",
  "details": "Please provide a valid query string"
}

{
  "error": "Unauthorized",
  "message": "API key is required"
}

{
  "error": "Proposal not found",
  "details": "No proposal found with ID: gov1x8jkz74"
}

{
  "error": "Failed to process enhanced AI analysis request",
  "details": "Internal server error occurred while processing the request"
}

Status Codes

Status Code	Description
200	Success - Analysis generated successfully
400	Bad Request - Invalid query parameters
401	Unauthorized - Missing or invalid API key
404	Not Found - Specified proposal not found
429	Too Many Requests - Rate limit exceeded
500	Internal Server Error

Notes

Content Sources: The API searches through various sources of content related to the proposal, including the proposal itself, technical references, and community discussions. These sources are used to generate a comprehensive analysis.

Response Time: Generating AI analysis for complex queries may take several seconds, especially for cross-proposal analysis that requires synthesizing information from multiple sources.

Proposal Types

The API supports analysis of all governance proposal types in the Cardano ecosystem:

Type	Description
InfoAction	Informational or action proposals
ParameterChange	Protocol parameter modifications
NewConstitution	Constitutional updates
TreasuryWithdrawal	Treasury fund allocations
HardForkInitiation	Hardfork trigger proposals
NoConfidence	No-confidence votes
UpdateCommittee	Constitutional committee changes

Overview

DRep API

Proposal API

Rationale API

Request Headers

Request Body

Response

Status Codes

Notes

Proposal Types

​Request Headers

​Request Body

​Response

​Status Codes

​Notes

​Proposal Types

Request Headers

Request Body

Response

Status Codes

Notes

Proposal Types